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 account2. Create a New Realm for the Egencia integration3. 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 definedData – an enterprise directory must be integrated with SecureAuth IdPWorkflow – the way in which users will access this application must be definedMulti-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 1. In the Profile Fields section, map the directory field that contains the user's Egencia ID to the SecureAuth IdP PropertyFor example, add the Egencia ID Field to the Email 2 Property if it is not already contained somewhere elseGlobal Aux Fields 2. Set Global Aux ID 1 to 1 Click Save once the configurations have been completed and before leaving the Data page to avoid losing changesPost Authentication 3. Select SAML 1.1 Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin4. 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 requiredUser ID Mapping 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 provide8. Select False from the Encode to Base64 dropdown SAML Assertion / WS Federation 9. Set the WSFed Reply To/SAML Target URL to https://www.egencia.com/pub/agent.dll/?qscr=grph&gpid=XXXXXXXXRetrieve the full URL from Egencia and replace the XXX appropriately10. 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 appropriately11. Set the WSFed/SAML Issuer to a Unique Name that will be shared with EgenciaThe WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Egencia side12. 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 appropriately13. Set the SAML Offset Minutes to make up for time differences between devices14. Set the SAML Valid Hours to limit for how long the SAML assertion is valid No configuration is required for the SAML Audience or SP Start URL fields 15. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertionIf using a third-party certificate, click Select Certificate and choose the appropriate certificate16. Provide the Domain in order to Download the Metadata File to send to Egencia (if required) SAML Attributes / WS Federation 17. Add AssertionValue in the Name field (Attribute 1)18. Set the Namespace (1.1) to http://www.egencia.com19. Select Global Aux ID 1 from the Value dropdown Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changesForms Auth / SSO Token 20. Click View and Configure FormsAuth keys / SSO token to configure the token/cookie settings and to configure this realm for SSO These are optional configurations To configure this realm's token/cookie settings, follow these steps:Forms Authentication 1. If SSL is required to view the token, select True from the Require SSL dropdown2. Choose whether SecureAuth IdP will deliver the token in a cookie to the user's browser or device:UseCookies enables SecureAuth IdP to always deliver a cookieUseUri disables SecureAuth IdP to deliver a cookie, and instead deliver the token in a query stringAutoDetect enables SecureAuth IdP to deliver a cookie if the user's settings allow itUseDeviceProfile enables SecureAuth IdP to deliver a cookie if the browser's settings allow it, no matter the user's settings3. Set the Sliding Expiration to True if the cookie remains valid as long as the user is interacting with the page4. Set the Timeout length to determine for how many minutes a cookie is valid No configuration is required for the Name, Login URL, or Domain fields Machine Key 5. No changes are required in the Validation field, unless the default value does not match the company's requirementIf a different value is required, select it from the dropdown6. No changes are required in the Decryption field, unless the default value does not match the company's requirementIf a different value is required, select it from the dropdown No configuration is required for the Validation Key or Decryption Key fields Authentication Cookies 7. Enable the cookie to be Persistent by selecting True - Expires after Timeout from the dropdownSelecting False - Session Cookie enables the cookie to be valid as long as the session is open, and will expire once the browser is closed or the session expires No configuration is required for the Pre-Auth Cookie, Post-Auth Cookie, or the Clean Up Pre-Auth Cookie fields Click Save once the configurations have been completed and before leaving the Forms Auth / SSO Token page to avoid losing changes To configure this realm for SSO, refer to SecureAuth IdP Single Sign-on Configuration To configure this realm for Windows Desktop SSO, refer to Windows desktop SSO configuration Egencia Configuration Steps Contact Egencia to enable the SAML functionality.