Docusign Integratio Invalid Security Token Was Provided. Incoming Username Token Must Contain Password
(Doc ID 2447990.1)
Last updated on MAY 04, 2020
Applies to:
PeopleSoft Enterprise SCM Supplier Contract Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Docusign integration invalid security token was provided. incoming Username token must contain password
An invalid security token was provided ---> The incoming Username token must contain password if the password option is set to be SendPlainText.
Electronic Signature Provider error: An invalid security token was provided ---> The incoming Username token must contain password if the password option is set to be SendPlainText. (10420,900)
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Log into docusign demo and under VP1, the owner, you need to add the user id and email that is allowed to sign documents to the account. So you need to edit the account information.
Then you go to the signature page in peoplesoft and add the user id and the email. All cases must match.
Once all of that is done you can validate and see if it is accepted.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |