Skip to main content
McAfee MVISION Cloud

SAP Concur SSO Integration with Azure AD via Proxy

To integrate SAP Concur SSO with Azure AD via Proxy, use the following procedure.

Prerequisites 

Before you begin, make sure you have the following prerequisites:

  • Admin access to Azure AD IdP.
  • Access to MVISION Cloud and appropriate role or rights to manage the SAP Concur service.
  • Admin access to SAP Concur.

Configure the SAML Proxy for SAP Concur

Perform the following activities to configure SAML proxy for SAP Concur.

Step 1: Download IdP Certificate from Azure AD

  1. Log in to Azure AD as an admin and go to Azure Active Directory > Enterprise Applications.
  2. Search for SAP Concur and add it.
  3. Click the SAP Concur app and select the Single Sign-On option to configure SSO.
  4. Under Set up Single Sign-On with SAML, click Edit.
    clipboard_eb706a5e8bfc321348f9321b11157eb71.png
  5. Under Basic SAML Configuration, configure the URIs based on the Users Concur instance and region. The instance name of the URI varies depending on the region. An example is shown below for URL format:

NOTE: For more details on the Concur Base URIs and regions, see Base URIs.

  1. Click Save.
  2. Under SAML Signing Certificate, click the Certificate (Base64) Download link to download the IdP (Azure) certificate and save it in your local folder. This is your IdP Certificate used to configure the SAML proxy in MVISION Cloud.
    clipboard_e0c99bc6b869b29599a6a9726f096fb33.png

Step 2: Download the SP Certificate from SAP Concur

  1. Log in to SAP Concur portal as admin with SSO permissions.
  2. Go to Administration > Company > Authentication Admin and click Manage Single Sign-On.
  3. Under the IdP Metadata section, select the existing IdP and view Metadata. Then proceed to export and save the metadata file in your local folder. This is your SP Certificate used to configure the SAML proxy in MVISION Cloud. 

Step 3: Configure SAML Proxy in MVISION Cloud

  1. Log in to MVISION Cloud.
  2. Go to Settings > Service Management.
  3. Select your SAP Concur instance from the Services list. (If no services are listed, contact MVISION Cloud Support for help.)
  4. Click the Setup tab, and under Proxy, click Get Started.
    clipboard_e6a70e0595d515eda4f66850964c40c1e.png

NOTE: To create and configure the proxy for the SAP Concur instance, see Configure Proxy for SAP Concur.

  1. Under Configure SAML, click Configure.
    clipboard_e952bd665d1e2ef6d3034246c03964e57.png
  2. Under Upload Identity Provider Certificate, upload the IdP Certificate downloaded earlier from Step 1 and click Next.
  3. Under Upload Service Provider Certificate, upload the SP Certificate downloaded earlier from Step 2 and click Next.
  4. Under Download SAML Certificate, download the Proxy Certificate and save it in your local folder. This certificate is used in Step 5.
  5. Once the SAP Concur SAML proxy configuration is successful, go to Actions > Edit Properties and add the following Company ID property.
    • Name: rewrite.additional.domain.names
    • Value: False
      clipboard_e0c318faeb472b19c101b12e11faaf6c7.png

Step 4: Configure SSO in Azure AD

  1. Log in to Azure AD admin portal.
  2. Go to Enterprise application > SAP Concur > Single Sign-on > SAML-based Sign-on.
  3. Click the pencil icon to edit Basic SAML Configuration. For Reply URL and Sign on URL, replace the Original URL (Concur domain) with the Proxy URL. For example,

Step 5: Add IdP Metadata in SAP Concur

SAP Concur allows only IdP configuration through metadata files. Before adding IdP metadata in Concur, make sure to modify the IdP metadata with the MVISION Cloud Certificate and URLs.

Modify IdP Metadata with MVISION Cloud Certificate and URLs

  1. Log in to SAP Concur portal as admin with SSO permissions.
  2. Go to Administration > Company > Authentication Admin and click Manage Single Sign-On.
  3. Under the IdP Metadata section, select the existing IdP and view Metadata. Then proceed to export and save the current IdP.
  4. Create another copy of this backup file and open the exported backup IdP metadata file and modify these:
    • Find the sections within the tags <X509Certificate> and </X509Certificate> and you might notice multiple sections with this tag. For each of these sections, replace the existing IdP Certificate with the MVISION Cloud Proxy Certificate downloaded earlier to configure SAML Proxy in Step 3
    • Find all instances of the word HTTP-Redirect and replace them with the word HTTP-POST. You should replace two matches near the bottom of the metadata file.
    • Notice at the bottom of the metadata file, there are three tag sections similar to:
      • <SingleLogoutService … HTTP- POST … />
      • <SingleSignOnService … HTTP- POST … />
      • <SingleSignOnService … HTTP-POST … />

Here, delete one of the repeated line section: <SingleSignOnService … HTTP-POST … />. Only one of the tag is required.

With the remaining two-line sections here, replace the quoted URL with the updated MVISION Cloud proxy domain URL and ensure the replacement is in URL encoded format:

<Original protocol>://<MVC proxy URL>/domain-access?shnsaml-request=<Original idP URL>/saml2

For example, <https://us-impl.api.concursolutions....hnsamlrequest=
https%3A%2F%2Flogin.microsoftonline.com%2F3c789172-fbb2-4850-b01c-c6a1b80e97fc%2Fsaml2

  1. Save the modified IdP Metadata file. This file is used in the next step Add IdP Metadata.

Add IdP Metadata

  1. Under IdP Metadata section, click Add.
  2. Under Add IdP Metadata, configure these:
    • Custom IdP Name. Enter a Custom IdP Name such as MVISION Cloud.
    • IdP Metadata. Either you can provide IdP’s metadata link or upload your IdP’s metadata file modified and saved in the previous step Modify IdP Metadata.
      clipboard_ec3976d82240b25ec04f6d64ac6f3c48a.png

Now an additional IdP (MVISION Cloud) is added to Concur.

  1. Make sure the SSO Setting is set to Optional. This allows seamless fallback to the original IdP and can be adjusted as needed.
  • Was this article helpful?