Ariba creates a web session, sets the session ID cookie in the user’s browser and saves the location of the final destination URL in the session.

Ariba looks up the applicable authentication method, which in this case will be SAML Corporate Authentication.This may be the homepage or a deep URL that a user has bookmarked, or received in an email. A user accesses the Ariba Sourcing or Ariba Buyer URL.The customer provides Ariba with a valid public certificate, a corporate login relay page URL and a logout URL.The user’s browser allows cookies and JavaScript.

The user must have an account created in Ariba Buyer where the Ariba UserID is identical to the user’s corporate account ID as specified in the SAML response Name ID.

In order for a customer to have access to Ariba, the following pre-requisites apply: Responsibility for the implementation of any SAML IdP on the customer side rests with the customer. There are several SAML Identity Provider (‘IdP’ hereafter) solutions which are offered by third-party vendors. This document gives examples of how the SAML Authentication may be implemented and is intended to illustrate the processes and concepts behind it. How to configure SAML Authentication for Ariba Buyer On-Premise? SAML Authentication for Ariba Buyer On-Premise

Ariba sign up