Skip to main content
Blog
Home/

App Passwords: More secure SOAP authentication using your existing code

Author Cassandra Loewen
Cassandra LoewenSenior API Technical Writer
Summary3 min read

Keep your SOAP integrations in compliance with upcoming Docusign go-live and API call requirements without having to update any of your code!

    • Additional resources

    Table of contents

    As followers of the Docusign Developer Blog might already know, our old legacy username/password authentication flow is being deprecated and will be unavailable for use after September 2022. For REST apps, this means switching to use an OAuth2 grant. For SOAP apps, this means switching to our new authentication flow: App Password. 

    In App Password authentication, your users create App Passwords, linked to their profiles, that they can use in place of their account password when going through auth to obtain access tokens. Any attempt to use an App Password to do something other than get an access token for an integration or make SOBO calls (such as attempting to log into their Docusign account via the website UI) will fail. This ensures that, even if an App Password is somehow compromised, the user’s account and data are still secure.

    We know that a lot of developers use legacy authentication, and not all of them can easily spare the time and resources to refactor the authentication code for their apps. Fortunately, you should be able to use the same legacy authentication code that’s already in your app to perform App Password auth! Both authentication flows use exactly the same steps and syntax; just pass in the user’s App Password rather than their account password and you should still get an access token.

    This means that you can switch to use a more secure way of authenticating users and stay in compliance with upcoming Docusign go-live and API call requirements without having to update any of your code! 

    You can read more about the advantages of App Passwords, see how to generate them, and find best practices on the Dev Center.

    Additional resources

    Author Cassandra Loewen
    Cassandra LoewenSenior API Technical Writer

    Cassandra has been writing for Docusign since early 2018. Since then, Cassandra has created a wide range of the guides, code examples, videos, and other content you can find throughout the Developer Center, particularly around Connect and Authentication. She currently lives outside of Seattle with her two Saint Bernard dogs, Zoe and Hagrid.

    More posts from this author

    Related posts

    • Developers

      Secure, verify, comply: Automate identity checks with Docusign APIs

      Author Niani Byrd
      Niani Byrd
      Secure, verify, comply: Automate identity checks with Docusign APIs
    • Reducing manual agreement work, part 1: Automating file export to cloud storage

      Author Julie Gordon
      Julie Gordon
      Reducing manual agreement work, part 1: Automating file export to cloud storage
    • Integrate seamless workflow automation to Salesforce with Docusign Maestro API

      Author Achille Jean Axel Nisengwe
      Achille Jean Axel Nisengwe
      Integrate seamless workflow automation to Salesforce with Docusign Maestro API

    Secure, verify, comply: Automate identity checks with Docusign APIs

    Author Niani Byrd
    Niani Byrd
    Secure, verify, comply: Automate identity checks with Docusign APIs

    Reducing manual agreement work, part 1: Automating file export to cloud storage

    Author Julie Gordon
    Julie Gordon
    Reducing manual agreement work, part 1: Automating file export to cloud storage

    Integrate seamless workflow automation to Salesforce with Docusign Maestro API

    Author Achille Jean Axel Nisengwe
    Achille Jean Axel Nisengwe
    Integrate seamless workflow automation to Salesforce with Docusign Maestro API

    Discover what's new with Docusign IAM or start with eSignature for free

    Explore Docusign IAMTry eSignature for Free
    Person smiling while presenting