Skip to main content
Conversation Starter
Feb 12, 2026 10:53 PM UTC
Solved

SOAP Calls Failing - "One or both of Username and Password are invalid."

Calling Login with https://www.docusign.net/api/3.0/credential.asmx fails with "One or both of Username and Password are invalid."  The Login call is made by using “[IntegratorKey]Username” as the username.

This just started recently.  I was only made aware of it today, so it could have started today.  All my customers are down. Is it possible that the API has changed and I never received any emails? We got our Integrators Key in 2013 and have not made any changes to this code in quite a while.

daveconAnswer
Conversation Starter
Feb 13, 2026 1:47 PM UTC

So, using the “App Password authentication” seemed to solve everything.

4 replies

daveconConversation StarterAuthor
Conversation Starter
Feb 13, 2026 1:50 AM UTC

A little more info, maybe not helpful, if I make the call and do not supply the integrators key, the call returns with an account and the base URL. But then if I make a call to RequestTemplates using the base URL and “/dsapi.asmx” (in this case “https://na2.docusign.net/api/3.0/dsapi.asmx”), I receive "One or both of Username and Password are invalid." and if I make the call to RequestTemplates and don’t provide the Integrator’s Key, I receive "The specified Integrator Key was not found or is disabled."

Translate
daveconConversation StarterAuthor
Conversation Starter
Feb 13, 2026 1:06 PM UTC

OK, so after doing the thing with not using the Integrators Key for the Login, my Apps & Keys dashboard now shows, “This app has used legacy authentication in the last 10 days.”, so it looks like the problem is that I need to use “App Password authentication” and the way it was being done has been deprecated. I just don’t know why I didn’t get any notice of that, I obviously need to get on that after this. I also noticed my key is listed as in the “Development” environment and there is a link to complete details to “Go Live”. Would that affect anything? I have a cert of compliance review and enabled in production from 2013. Would that maybe have been demoted bc of the legacy authentication (even though moving to App Password authentication would not have any effect on code)?

Translate
daveconConversation StarterAuthorAnswer
Conversation Starter
Feb 13, 2026 1:47 PM UTC

So, using the “App Password authentication” seemed to solve everything.

Translate
daveconConversation StarterAuthor
Conversation Starter
Feb 13, 2026 1:48 PM UTC

Can someone tell me why my key is not in production anymore and whether I should go through the steps to move that into production?

Translate