The Shibboleth V2 IdP and SP software have reached End of Life and are no longer supported. This documentation is available for historical purposes only. See the IDP v4 and SP v3 wiki spaces for current documentation on the supported versions.

Concur Solutions

Concur Solutions considers themselves "SAML compatible but not SAML compliant". Essentially this means there are many limitations in their SSO implementation, and integration with a Shibboleth IdP is quite non-intuitive and non-standard. For example,

  • Concur does not share their SP metadata, and does not consume IdP metadata via SAMLP. Instead they require unsolicited, or IdP-initiated, SSO sessions.
  • Concur requires the IdP signing certificate to be supplied via email.
  • Concur ignores SAML attributes and looks only in the SAML subject for a NameID containing an identifier in the form The userID in this case is the identifier provisioned to Concur via file transfer from the HR or ERP system.

The Concur SAML integration guide, and Concur mobile app integration guide, are provided only under NDA. However, the steps here should help establish the SSO partnership.

Concur integration with Shibboleth IdP

  1. Provide a copy of the IdP signing certificate to Concur via email.
  2. Ensure IdP-initiated SSO is enabled in the IdP.
    1. This is enabled by default in Shibboleth IdP 2.3.0 and above.
  3. Configure the Concur SP metadata into the IdP (modified version provided here).
    1. Provide the metadata to the IdP file system, then configure it into relying-party.xml.
    2. Ensure the NameIDFormat in the SP metadata matches the nameFormat used in the AttributeEncoder of the AttributeDefinition in attribute-resolver.xml.

      <md:EntityDescriptor entityID=""
        <md:SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
              <mdui:DisplayName xml:lang="en">Concur Solutions</mdui:DisplayName>
      <!--    <mdui:Description xml:lang="en">Optional description.</mdui:Description> -->
              <mdui:Logo height="146" width="148"></mdui:Logo>
          <md:AssertionConsumerService index="1" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location=""/>
  4. Define a NameID attribute in attribute-resolver.xml to be released to Concur.

    1. Ensure the NameFormat used in the Attribute Encoder matches the NameIDFormat specified in the SP metadata.
    2. See

    3. Also see

      <resolver:AttributeDefinition xsi:type="ad:Template" id="ConcurID"> 
          <resolver:Dependency ref="myLDAP" />
          <resolver:AttributeEncoder xsi:type="enc:SAML2StringNameID" nameFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:unspecified" />
  5. Release that attribute to Concur in attribute-filter.xml.

    <afp:AttributeFilterPolicy id="releaseToConcur">
      <afp:PolicyRequirementRule xsi:type="basic:AttributeRequesterString" value="" />
      <afp:AttributeRule attributeID="ConcurID">
        <afp:PermitValueRule xsi:type="basic:ANY" />
  6. Exclude Concur from receiving the transcientId in attribute-filter.xml.
    1. Concur cannot receive any released attributes other than the ConcurID.

    2. A basic transientId release policy might look like this.

      <afp:AttributeFilterPolicy id="releaseTransientIdToAnyone">
          <afp:PolicyRequirementRule xsi:type="basic:NOT">
              <basic:Rule xsi:type="basic:AttributeRequesterString" value="" />
          <afp:AttributeRule attributeID="transientId">
              <afp:PermitValueRule xsi:type="basic:ANY"/>
  7. Disable assertion encryption and NameID encryption for Concur in relying-party.xml.

    1. Insert this configuration below the Default Relying Party configuration. 

    2. See

      <rp:RelyingParty id="" provider="" defaultSigningCredentialRef="IdPCredential">
        <rp:ProfileConfiguration xsi:type="saml:SAML2SSOProfile" encryptAssertions="never" encryptNameIds="never" />
  8. Construct and test an unsolicited URL.
    1. For example,