ºÚÁϺ£½Ç91Èë¿Ú

Integrate with Concur Travel and Expense

Use ºÚÁϺ£½Ç91Èë¿Ú SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications with a single set of credentials.

Read this article to learn how to integrate with Concur Travel and Expense. 

Prerequisites

  • A ºÚÁϺ£½Ç91Èë¿Ú administrator account
  • ºÚÁϺ£½Ç91Èë¿Ú SSO Package or higher or SSO à la carte option
  • A Concur Travel and Expense user account with the Company Administration (Travel) permission
  • Your Concur domain and region

Creating a new ºÚÁϺ£½Ç91Èë¿Ú Application Integration

  1. Log in to the .
  2. Go to USER AUTHENTICATION &²µ³Ù;ÌýSSO Applications.
  3. Click + Add New Application.
  4. Type the name of the application in the Search field and select it.
  5. Click Next.
  6. In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.

Note:

If this is a Bookmark Application, enter your sign-in URL in the Bookmark URL field.

  1. Optionally, expand Advanced Settings to specify a value for the SSO IdP URL. If no value is entered, it will default to https://sso.jumpcloud.com/saml2/<applicationname>.

Warning:

The SSO IdP URL is not editable after the application is created. You will have to delete and recreate the connector if you need to edit this field at a later time.

  1. Click Save Application.
  2. If successful, click:
    • Configure Application and go to the next section
    • Close to configure your new application at a later time

Configuring the SSO Integration

To configure ºÚÁϺ£½Ç91Èë¿Ú

  1. Create a new application or select it from the Configured Applications list.
  2. Select the SSO tab.
  3. Replace any instances of YOURDOMAIN or YOUR_REGION with your information.
  4. Add or change any attributes.
  5. Click save.

Download the ºÚÁϺ£½Ç91Èë¿Ú metadata file

  1. Find your application in the Configured Applications list and click anywhere in the row to reopen its configuration window.
  2. Select the SSO tab and click Export Metadata.
  3. The ºÚÁϺ£½Ç91Èë¿Ú-<applicationname>-metadata.xml will be exported to your local Downloads folder.

Tip:

Metadata can also be downloaded from the Configured Applications list. Search for and select the application in the list and then click Export Metadata in the top right corner of the window.

To configure Concur Travel and Expense

  1. Log in to the SSO management page based on the region your Concur entity is hosted in:
    1. US:https://www.concursolutions.com/nui/authadmin/ssoadmin
    2. EMEA: https://eu1.concursolutions.com/nui/authadmin/ssoadmin
    3. China: https://www.concurcdc.cn/nui/authadmin/ssoadmin
  2. Navigate to Administration > Company > Authentication Admin > Manage Single Sign-on.
  3. In IdP Metadata, click Add and enter the following information:
    • Custom IdP Name - enter ºÚÁϺ£½Ç91Èë¿Ú
    • Logout URL - enter https://console.jumpcloud.com/userconsole (this will return users to the ºÚÁϺ£½Ç91Èë¿Ú user console when they log out)
    • Click Upload XML File and upload the ºÚÁϺ£½Ç91Èë¿Ú metadata generated in the previous section.
    • Optionally, hide the sign-in option from users on mobile and signing in through concursolutions.com by selecting Hide this SSO option from users signing in to Concur on web or mobile.
  4. Click Add Metadata.
  5. After testing SSO, in the Enable SSO section, change the settings to SSO Required.
    • If you change the SSO setting to SSO Required, all users will be required to sign in to concursolutions.com through an IdP using SSO. Users—including TMCs, admins, web services, and test user accounts—will be blocked from signing in to concursolutions.com with their username and password. This could cause a disruption in services for those users.
    • Best Practice is to use the SSO Optional setting until all users understand how to sign in with SSO. Before you change the setting to SSO Required, we recommend you provide your users with a 60-day notice or a notification timeframe that is standard for your organization.

Important:

Changing the SSO Setting to SSO Required affects both web and mobile sign-in. Beginning with the 9.86 (November) version of the SAP Concur mobile app, changing the SSO Setting to SSO Required mandates that users must sign in using SSO on both web and mobile platforms.

Authorizing User SSO Access

Users are implicitly denied access to applications. After you connect an application to ºÚÁϺ£½Ç91Èë¿Ú, you need to authorize user access to that application. You can authorize user access from the Application Configuration panel or from the Groups Configuration panel. 

To authorize user access from the Application Configuration panel

  1. Log in to the .
  2. Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
  3. Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
  4. Select the check box next to the group of users you want to give access.
  5. Click save

To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.

Validating SSO user authentication workflow(s)

IdP-initiated user workflow

  • Access the
  • Go to Applications and click an application tile to launch it
  • ºÚÁϺ£½Ç91Èë¿Ú asserts the user's identity to the SP and is authenticated without the user having to log in to the application

SP-initiated user workflow

  • Go to the SP application login - generally, there is either a special link or an adaptive username field that detects the user is authenticated through SSO

Note:

This varies by SP.

  • Login redirects the user to ºÚÁϺ£½Ç91Èë¿Ú where the user enters their ºÚÁϺ£½Ç91Èë¿Ú credentials
  • After the user is logged in successfully, they are redirected back to the SP and automatically logged in

Removing the SSO Integration

Important:

These are steps for removing the integration in ºÚÁϺ£½Ç91Èë¿Ú. Consult your SP's documentation for any additional steps needed to remove the integration in the SP. Failure to remove the integration successfully for both the SP and ºÚÁϺ£½Ç91Èë¿Ú may result in users losing access to the application.

To deactivate the SSO Integration

  1. Log in to the .
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to deactivate and click to open its details panel. 
  4. Select the SSO tab.
  5. Scroll to the bottom of the configuration.
  6. Click Deactivate SSO
  7. Click save
  8. If successful, you will receive a confirmation message.

To delete the application

  1. Log in to the .
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to delete.
  4. Check the box next to the application to select it.
  5. Click Delete.
  6. Enter the number of the applications you are deleting
  7. Click Delete Application.
  8. If successful, you will see an application deletion confirmation notification.
Back to Top

List IconIn this Article

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case