Hi Marco,

Thank you for contacting us on this.

Since your organization has a 2-step authentication, you can use the OAuth as for a creation of a project as well for adding a project to your existing solution. Exactly this type of authentication was implemented to handle 2-factor login to an org (besides other OAuth benefits :) ).

Also, there is no data about failed attempts to log in from the IDE to an org in the described case due to the 2-step authentication. We will investigate this more detailed.

Please let me know if using OAuth is what you are looking for to solve the issue when adding a new project to your existing solution.

Thank you,

Kate

I see; 

So it doesn't work properly because we have a 2-step authentication. 

I haven't tried the Oauth tickbox, I'll do that. I hope I don't have to enter credentials every time I deploy then...

It might be a nice adition if you put a hover over help thing explaining that the token login doesn't show the 2nd step in the 2-step authentication. 

But thanks for resolving this. 

Hi Marco,

Thank you for your response and for your suggestion to add the hover - we like this idea and this would be useful for sure!

As for using the OAuth type of authentication, you shouldn't log in every time to deploy - there is a session time that you can set up on your organization, and the IDE would require to re-login when a session between TWS and your org would be expired. In this cases, you would get a notification in the IDE with an option to re-authorize.

Also, you can find additional details about OAth here.

Regards,

Kate