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 'https://refeds.org/profile/mfa' set as the only authenticationContextClassRef, then it MUST force the user to login with MFA.  Optionally, if the IdP receives 'https://refeds.org/profile/mfa' 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', 'http://id.incommon.org/assurance/base-level', and 'https://refeds.org/profile/mfa' 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 'https://refeds.org/profile/mfa' 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

Related IdP Configuration Links

Initial RAO Onboarding (Existing RAOs)

InCommon staff will need to onboard RAOs by sending an invitation email from CCM.  Once an institution's IdP is ready, an RAO should send an email to pcaskey@internet2.edu and request such onboarding.

 The initial login matches the asserted email address to the email address stored in the CCM user profile.

At that point, the asserted eppn is added to the "IdP User ID" field in the CCM user profile.

All future logins will use asserted values for first/last name and email address to update the respective fields in the CCM user profile.

RAOs can then onboard their DRAOs using the same invitation function (or by manually entering their eppn in CCM).    ← NOTE: Due to a default permissions issue, this will not be functional until 9/13/17.

Onboarding Existing Users

Once logged into CCM, here’s how to onboard existing RAOs/DRAOs in your org:

https://spaces.at.internet2.edu/pages/viewpage.action?pageId=115180856    (temporarily restricted, awaiting dev fix on 9/13/17)

Config Contributions

Change in general-authn.xml:
-- Add new 2fa supported principal to both authn/Duo, and authn/MFA --
<bean parent="shibboleth.SAML2AuthnContextClassRef" c:classRef="https://refeds.org/profile/mfa" />

...and then just add a release rule to attribute-filter.xml:
<afp:AttributeFilterPolicy id="Incommon_Certmanager">     
  <afp:PolicyRequirementRule xsi:type="basic:AttributeRequesterString" value="https://cert-manager.com/shibboleth" />
  <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" />