 |
| ||||||||
SC-9402
This feature adds support for OAuth authentication in SAP Ariba Contracts integrated with the DocuSign application. DocuSign is used to obtain electronic signatures for contracts. Buyers can send a contract to DocuSign or revoke a contract from DocuSign using the OAuth authentication method. When a buyer submits a signature task, the OAuth authentication method uses dynamically generated access tokens to log in to DocuSign.
Today SAP Ariba Contracts uses credentials based authentication for integrating with DocuSign. The current method required customers to enter the credentials (username / password) of their DocuSign account in SAP Ariba.
Improves Security and moves to a more modern authentication mechanism. This feature introduces the OAuth authentication method for SAP Ariba Contracts integrated with the DocuSign application. Buyers can access the DocuSign application with unique access tokens that are dynamically generated for each DocuSign user.
The OAuth authentication method is also implemented for Non-Disclosure Agreement (NDA) contracts in SAP Ariba Contracts.
Customer Configured
Today SAP Ariba Contracts uses credentials-based authentication for integrating with DocuSign. The current method required customers to enter the credentials (username/password) of their DocuSign account in SAP Ariba.
SC-9402
This feature adds support for OAuth authentication in SAP Ariba Contracts integrated with the DocuSign application. DocuSign is used to obtain electronic signatures for contracts. Buyers can send a contract to DocuSign or revoke a contract from DocuSign using the OAuth authentication method. When a buyer submits a signature task, the OAuth authentication method uses dynamically generated access tokens to log in to DocuSign.
Improves Security and moves to a more modern authentication mechanism. This feature introduces the OAuth authentication method for SAP Ariba Contracts integrated with the DocuSign application. Buyers can access the DocuSign application with unique access tokens that are dynamically generated for each DocuSign user.
The OAuth authentication method is also implemented for Non-Disclosure Agreement (NDA) contracts in SAP Ariba Contracts.
What's New Guide
SC-9402: OAuth Authentication for DocuSign in SAP Ariba Contracts
Customer Configured
| Roadmap / Commitment: | SAP |
| Planned GA Month: | 2011 |
| Jira Status: | Deployed GA |
| Readiness Model: | High Touch |
| Customers Committed: | Starbucks |
| Feature Toggle ID: | SC-9402 |
2011 Readiness Feature Preview: OAuth authentication for DocuSign in SAP Ariba Contracts (SC-9402)
SAP Ariba Contracts
SAP Ariba Strategic Sourcing Suite
General
-
Enable the Application.ACM.Signature.DocuSignREST.OAuth.Enabled parameter in the Manage Administration Intelligent Configuration Manager page of the SAP Ariba Contracts solution. For information about the parameter, see Enable OAuth authentication for DocuSign in SAP Ariba Contracts.
-
Your site administrator must grant consent for OAuth in SAP Ariba Contracts. For information about granting consent for OAuth, see How to grant admin-user consent for OAuth in SAP Ariba Contracts. After your site administrator grants consent for OAuth, you can initiate a signature task to send contracts to DocuSign for electronic signatures.
- You must enable DocuSign for your site and also specify the DocuSign parameters such as the DocuSign account ID. If you do not know the DocuSign account ID, check with DocuSign.
- Your organization must have a single administrator account with DocuSign. The account ID will be the ID for the administrator account with DocuSign. For more information, see the Enabling electronic signatures in contracts section in the Contract administration guide.
- To send contracts from SAP Ariba Contracts to DocuSign for electronic signatures, you must have your site administrator grant access to the OAuth authentication in the SAP Ariba Administrator page. See How to grant an admin user consent for OAuth in SAP Ariba Contracts.
- To submit a document to DocuSign, the task owner must have a DocuSign user account associated with the company’s administrator account. This account must be registered to the same email account configured for the task owner on the SAP Ariba server.
NDA Contracts
- The Non-Disclosure Agreement Contract functionality requires your Designated Support Contact to log a Case to enable it. An SAP Ariba Customer Support representative will follow up to complete the request.
- You must be a part of either the NDA User or the NDA Admin User group to be able to administer NDAs.
- Buyers cannot submit a signature task in SAP Ariba Contracts without the admin user consent for OAuth. If the buyer tries to submit a signature task for a contract without the admin user consent for OAuth, the following error is displayed:
- Admin consent is required.
For more information, see How to grant an admin user consent for OAuth in SAP Ariba Contracts. - The error is displayed for any type of signature task submitted without the admin user consent; signature tasks such as New Round, Withdrawal, Update, and so on.
- This restriction is also applicable to a signature task initiated for an NDA contract. Buyers cannot send an NDA contract to DocuSign or revoke an NDA contract from DocuSign without the admin user consent for OAuth.
User not able to submit signature task, error "USER_NOT_FOUND" occurs while submitting the task.
When user tries to complete Grant access process gets an error message.
Strategic Contracts 2011
Strategic Sourcing 2011