SCIM user provisioning with SAP Concur

Tim Nied 1 Reputation point

SAP Concur released a new UPS v4 (SCIM capable) API. Details can be found here: The goal is to simplify authentication and user provisioning for Azure AD customers with SAP Concur. It appears that the type of access token (JWT) created from Concur's side may cause some issues with creating the connection. Is there a workaround if the access token is in the JWT format? Thank you in advance for your help.

Authentication is outlined here:

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,542 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Danny Zollner 9,861 Reputation points Microsoft Employee

    Could you elaborate on why you think the JWT type of token causes issues with provisioning, and what those issues are? AAD Provisioning can utilize JWT bearer tokens. Looking at the authentication/authorization documentation you provided, it confirms that they expect the access token to be provided in the Authorization header as bearer XYZ, which should work fine with AAD Provisioning.

    1 person found this answer helpful.