Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


The goal of the needed Shibb IdP config mentioned below can be simply stated as this:

"If the IdP receives a SAML authentication request with '' set as the only authenticationContextClassRef, then it MUST force the user to login with MFA.  Optionally, if the IdP receives '' in a list of multiple allowed authentication contexts, it MAY ask the user if they would like to authenticate with MFA."

The InCommon Cert Service SSO/MFA flow works like this:

  1. User clicks federated login link.

  2. User selects IdP from discovery service

  3. IdP receives SAML authenticationRequest with 'Password', 'PasswordProtectedTransport', '', and '' set as the allowed/requested SAML authenticationContextClassRef values.

  4. IdP optionally asks user if they want to use MFA authentication

  5. SP/app receives SAML assertion with user's ePPN.

  6. SP/app looks up user's invitation and determines if the user is an RAO.

  7. If the user is an RAO, then the SAML authenticationContextClassRef in the received assertion is checked.

  8. If the RAO user did not authenticate with MFA, they are sent back to the IdP with only '' set as the allowed/requested SAML authenticationContextClass (since the user was identified as an RAO).  Otherwise, the user is a DRAO and they are logged in.

Comodo Certificate Manager (CCM) SAML SP entityID  (present in the InCommon metadata aggregate)

Required Attributes

  • Both eppn and email address are required.  

    • EduPersonPrincipalName [eppn]  (SAML: urn:oid:

    • Email address [mail]  (SAML: urn:oid:0.9.2342.19200300.100.1.3)  

  • First and last name are optional.

    • First name [givenName]  (SAML: urn:oid:

    • Last name [sn]  (SAML: urn:oid:

  • For the initial invitation, the email address asserted by the IdP must match the email address in the invited user’s CCM profile.  At that point, the user’s eppn is stored in their CCM profile.

  • Thereafter, only a match on eppn is required to bind the user to their CCM profile.

  • The user’s eppn can be edited directly in CCM.

  • After the initial login, values for email address, first name, and last name received from the IdP will be used to update the related values in the user’s CCM profile

Onboarding Existing Users

Once logged into CCM, here’s how to onboard existing RAOs/DRAOs in your org:    (temporarily restricted, awaiting dev fix on 9/13/17)

Config Contributions

For IdP 3.3.x
Change in general-authn.xml:
-- Add new 2fa supported principal to both authn/Duo, and authn/MFA --
<bean parent="shibboleth.SAML2AuthnContextClassRef" c:classRef="" />

...and then just add a release rule to attribute-filter.xml:
<afp:AttributeFilterPolicy id="Incommon_Certmanager">     
  <afp:PolicyRequirementRule xsi:type="basic:AttributeRequesterString" value="" />
  <afp:AttributeRule attributeID="email">
    <afp:PermitValueRule xsi:type="basic:ANY" />
  <afp:AttributeRule attributeID="givenName">
    <afp:PermitValueRule xsi:type="basic:ANY" />
  <afp:AttributeRule attributeID="surname">
    <afp:PermitValueRule xsi:type="basic:ANY" />
  <afp:AttributeRule attributeID="eduPersonPrincipalName">
    <afp:PermitValueRule xsi:type="basic:ANY" />

  • No labels