Release Update KB0409121
Email
[Demo linked] OAuth authentication and REST integration for Adobe Sign in SAP Ariba Contracts
Feature ID

SC-12238

Feature Description

This feature enables the integration of SAP Ariba Contracts and Adobe Sign by using REST APIs. The integration of SAP Ariba Contracts and Adobe Sign now supports the use of OAuth 2.0 authentication method to send documents from SAP Ariba Contracts to Adobe Sign for eSignatures.

Customer Problem

Adobe has scheduled the planned end-of-life for the SOAP based APIs for the integration for Adobe Sign. With the end-of-life of these APIs, it is imperative to upgrade the integration between SAP Ariba Contracts and Adobe Sign to the new integration standards.

Customer Value Proposition

The new REST APIs contain functionality to address persistent customer issues with the current integration. In addition, OAuth 2.0 provides a more secure authentication architecture and an improved user experience.

Audience

Buyer

What's New Guide

https://help.sap.com/docs/SAP_Ariba/978b7e36451a4c2c85321a3ef6f3a7e5/f46756811fdc47259c235ebc00a89dc2.html?locale=en-US&state=PRODUCTION&version=cloud

Feature Enablement

Mandatory w/ Opt-in Period

Feature ID: SC-12238
Demo:
Feature at a Glance

2202 Readiness Feature Preview: OAuth authentication and REST integration for Adobe Sign in SAP Ariba Contracts

Applicable Solutions

SAP Ariba Contracts
SAP Ariba Strategic Sourcing Suite

Prerequisites

To integrate SAP Ariba Contracts and Adobe Sign using REST APIs and OAuth authentication, you must set the following parameter to Yes in the Manage / Administration / Intelligent Configuration Manager page of the SAP Ariba Contracts solution: Application.ACM.Signature.AdobeSignREST.Enabled
For more information about the parameter, see Integrate SAP Ariba Contracts with Adobe Sign by using REST APIs.

You must configure Adobe Sign for eSignatures in your site. For more information, see Contract administration guide.

To send documents from SAP Ariba Contracts to Adobe Sign for eSignatures, you must have your site administrator grant access to OAuth authentication in the SAP Ariba Administrator page. For more information, see How to grant admin-user consent for OAuth between SAP Ariba Contracts and Adobe Sign.

You must have created new users with Group Admin permissions in AdobeSign. Only users with the Group Admin permission in AdobeSign can grant consent from the SAP Ariba Administrator page of SAP Ariba Contracts.

Restrictions

Buyers cannot submit a signature task from SAP Ariba Contracts to Adobe Sign without the admin-user consent for OAuth. If buyers submit a signature task for a document without the admin-user consent for OAuth, the following error is displayed:

The task has been created but cannot be submitted. Reason: Error in getting the Transient ID for the document :<document name> : Access token provided invalid or has expired To resubmit the task after resolving this issue, view task details and click Submit.

For more information, see How to grant admin-user consent for OAuth between SAP Ariba Contracts and Adobe Sign.

The error is displayed for any type of signature task submitted without the admin user consent; signature tasks such as Submit, New Round, Withdrawal, Update, and so on.

Note: OAuth uses access tokens and refresh tokens for authentication. If OAuth uses a refresh token, and if the refresh token expires, the following message is displayed:

The task has been created but cannot be submitted. Reason: Error in getting the Transient ID for the doument :<document name> : Refresh token is provided invalid or has expired To resubmit the task after resolving this issue, view task details and click Submit.

Users must grant admin-user consent to Adobe Sign when the above message is displayed.

Buyers cannot send documents for eSignatures from SAP Ariba Contracts to Adobe Sign if they do not belong to the Group ID registered for Adobe Sign integration in SAP Ariba Contracts.

If a user who does not belong to the Group ID registered for Adobe Sign in SAP Ariba Contracts tries to initiate a signature task, the following error is displayed:

The task has been created but cannot be submitted. Reason: Error in getting the Transient ID for the doument :<document name> : The API caller does not have the permission to execute this operation To resubmit the task after resolving this issue, view task details and click Submit.
The Auto add user option is no longer available to automatically create a Adobe Sign user account when a user sends the document for eSignature to Adobe Sign.

Users who initiate a signature task in SAP Ariba Contracts must always have an active account with Adobe Sign. These users must belong to the Group ID configured in the Signature Providers page of the SAP Ariba Contracts solution.


Applies To

Strategic Contracts 2202
Strategic Sourcing 2202

Terms of Use  |  Copyright  |  Security Disclosure  |  Privacy