Hi Tim,

Thank you very much for such a feedback!

TWS stores your Salesforce credentials in the project file in an encrypted way. You can find and ensure it in the folder of the project in the ‘Documents’ -> ‘The Welkin Suite’ -> ‘Projects’ -> a folder of a project. There you should find the SFPROJ File (.sfproj) and open it with any text editor. You will see the field with Login, and encrypted fields with Password and Security Token.

Our future plans are to exclude the password from the project file.

So once you share your project with somebody, it will be possible to connect to this Org with the credentials which you have entered but the password and security token will stay unknown.

At the same time, I should admit that the push to the Subversion repository isn’t currently supported.

Thank you,

Kate

I tested to see if I could simply remove the Login/Password/SecurityToken values from the .sfproj file, and got interesting results.  I emptied those three fields in the .sfproj file, hoping that TWS would prompt me for new credentials the next time I opened it.  Before re-opening the project file, lines 7-9 looked like the following:

    <Login></Login>
    <Password></Password>
    <SecurityToken></SecurityToken>

Then I opened the file, and saw the following prompt:  "Couldn't login to Salesforce with your account settings."  Great!  Now I expect to change the properties in the project to reflect my own personal credentials.  So I right-click on the project in the solution explorer, select "Properties", and then enter my credentials.  Then I save the project and exit.  Then when I open the .sfproj file XML, I see my re-entered credentials UNENCRYPTED.

    <Login>sampleLogin</Login>
    <Password>samplePassword</Password>
    <SecurityToken>sampleToken</SecurityToken>

:-o

Hi Tim,

Thank you for your investigation!

We are glad that you have brought this issue to our attention.

Thanks to the investigation that we did after your notification, we have found that this is the reason of the following issue: changed credentials are not accepted by TWS at all. Since credentials were encrypted during the recording to the project file at the first entering, the changed ones rewrite these credentials and they are perceived as already encrypted. So further work on the project is stopped.

This has been added now to our backlog and to the current sprint.

Next week we are going to release the TWS version which will include the fix of this issue.

Thank you and have a nice day!

Kate

Hi Tim,

We have released the new version of The Welkin Suite.

Current issue with changed project credentials is fixed.

Please let us know if this is solved for you.

Thank you,

Kate