Skip to main content

Egencia (SAML 1.1) Integration Guide

Introduction

Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML 1.1 to Egencia.

Prerequisites

1. Have an Egencia account

2. Create a New Realm for the Egencia integration

3. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:

  • Overview – the description of the realm and SMTP connections must be defined

  • Data – an enterprise directory must be integrated with SecureAuth IdP

  • Workflow – the way in which users will access this application must be defined

  • Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined

SecureAuth IdP Configuration Steps

Data

44832385.png

1. In the Profile Fields section, map the directory field that contains the user's Egencia ID to the SecureAuth IdP Property

For example, add the Egencia ID Field to the Email 2 Property if it is not already contained somewhere else

Global Aux Fields

44832386.png

2. Set Global Aux ID 1 to 1

Warning

Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Post Authentication

44832708.png

3. Select SAML 1.1 Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin

4. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/InterSiteTransfer.aspx)

5. A customized post authentication page can be uploaded, but it is not required

User ID Mapping

60564688.png

6. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Egencia ID (Email 2)

7. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)

Select a different option if Egencia requires it, which the SP will provide

8. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation

44832383.png

9. Set the WSFed Reply To/SAML Target URL to https://www.egencia.com/pub/agent.dll/?qscr=grph&gpid=XXXXXXXX

Retrieve the full URL from Egencia and replace the XXX appropriately

10. Set the Consumer URL to https://www.egencia.com/pub/agent.dll/?qscr=sson&gpid=XXXXXXXX

Retrieve the full URL from Egencia and replace the XXX appropriately

11. Set the WSFed/SAML Issuer to a Unique Name that will be shared with Egencia

The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Egencia side

12. Set the SAML Recipient to https://www.egencia.com/pub/agent.dll/?qscr=sson&gpid=XXXXXXXX

Retrieve the full URL from Egencia and replace the XXX appropriately

13. Set the SAML Offset Minutes to make up for time differences between devices

14. Set the SAML Valid Hours to limit for how long the SAML assertion is valid

Note

No configuration is required for the SAML Audience or SP Start URL fields

70489017.png

15. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion

If using a third-party certificate, click Select Certificate and choose the appropriate certificate

16. Provide the Domain in order to Download the Metadata File to send to Egencia (if required)

SAML Attributes / WS Federation

44832382.png

17. Add AssertionValue in the Name field (Attribute 1)

18. Set the Namespace (1.1) to http://www.egencia.com

19. Select Global Aux ID 1 from the Value dropdown

Warning

Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token

Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.

44833086.png

Egencia Configuration Steps

Contact Egencia to enable the SAML functionality.

In this section: