SuccessFactors OAuth 2.0 SAML bearer assertion flow

[Alberto Gonz_le]

• SuccessFactors Basic authentication method will be removed on 1^st November 2022. In that sense everyone is forced to move to OAuth.
• The OAuth grant flow that will use SuccessFactors will be SAML Bearer Assertion.
• This grant flow is not supported natively by ServiceNow, right now only are available Authorization Code, Resource Owner Password Credentials, Client Credentials and JWT Bearer.
• We have raise a ticket in HI to know if it will be included in future releases, right now for Rome is not available and the spoke configuration for SuccessFactors only allows Basic auth.

The procedure described in SuccessFactors to get that access_toke will be:

• Step 1: Call the endpoint https://<api-server>/oauth/idp providing the parameters client_id, user_id, token_url, private_key (created in SuccessFactors as certificate not compatible with PEM when importing in ServiceNow). The response will be a SAML assertion.
• Step 2: Call the endpoint https://<api-server>/oauth/token using the SAML assertion provided in step 1, the parameters will be client_id, grant_type (value is urn:ietf:params:oauth:grant-type:saml2-bearer), company_id, assertion (provided in step 1). The response will be a token that will be sent as part of the Bearer token authorization to pull data when call to the rest of endpoints. The response doesn't provides a refresh_token value.

Is possible to have this functionality natively supported by ServiceNow or a customization is needed?

[Community Alums]

Hi Alberto,

Posting on old post, Unsure if you have got answer or not, but here is the information:

Currently Servicenow does not support OAuth 2.0 - its intended in April release - PRB1531529 is Servicenow's internal PRB.

Regards,

Asad.

[Emile Hermans]

Is there already a best practice scenario (ootb) avaliable?