This section provides information on requesting and using a Docusign encrypted password in the SOAP api.asmx API where the wsse security header is used for authentication.
"},"sys":{"type":"Entry"},"internal":{"type":"ContentfulAssemblyHtmlSection"}},{"id":"65fde919-1d57-5f44-998d-8510e71bc5c2","contentful_id":"3nFcloXRAD3MQNSQmfn8K6","node_locale":"en-US","heading":"Step 1. Find user account","headingLevel":2,"sectionId":null,"multicolumn":true,"noBorder":false,"backgroundKind":null,"paddingTop":null,"paddingBottom":null,"html":{"html":"To start the process, use the Credential Login API to find the accounts associated with the user’s credentials. This initial call uses the email address and clear text password.
The response shows that this user has access to two accounts and the BaseUrl shows that one account is on “test” while the second account is on “test2”. In future API calls, you will select the server and endpoint as appropriate for the account you will use. For the example we will use:
\nAccount = https://test.docusign.net/api/3.0\nUserId = 47c97f72-xxxx-xxxx-xxxx-75ac3b630bfa\n\n
Note: The email address can be used instead of the UserId in API calls.
\nNext, request the encrypted Password for the user by making a GetEncryptedPassword request to the server where this user’s account is located and providing the credentials in the X-Docusign-Authentication header.
The response returns the encrypted version of the password, such as SBXBCN...9LZuk= .
At this point, if client application (securely) stores the BaseUrl, UserId and encrypted password, then the application does not need to repeat the previous calls unless authentication fails on successive calls.
The following request shows how the encrypted password is used, along with the Integrator Key and UserId, to authenticate a Request Status call for an envelope. This same pattern would be used in all successive API calls.
In this case the Integrator Key is [DOCU-KEY-ABC2].