Last modified 6 years ago Last modified on 06/05/14 16:32:50

IAM / Projects / Shibboleth / Service Integrations / Blackboard Connect

The three BBC services for UA are:

Staging service:

Recipient Portal:

Sender Portal:

SAML Profile - Unsolicited SSO

see "Connect SSO Implementation Manual" (too large to attach)

BBC uses "unsolicited" or "IdP initiated" SSO. That means that, rather than responding to a user's request and redirecting the user's browser to the IdP for authentication and attributes, BBC requires us to send a SAML assertion with user authentication and required attributes. This is accomplished in the Shibboleth IdP by setting up a URL that invokes a profile (or "end point") specifically for unsolicited SSO ("idp/profile.SAML2/Unsolicited/SSO") and includes the (encoded) relying party entity id above.

BBC also crafts the entityID [~URL] of the service based on the certificate used to sign the SAML assertion (attached). Note that means that if and when the UA IdP certificate is changed, these entity IDs will change, requiring changes to the sp-metadata file, the relying-party.xml file, and the attribute-filter.xml files, as each of these requires the explicit entity ids of the services to which the IdP will send assertions.

For BBC entities above, those URLs are:

Staging service:

Recipient Portal:

Sender Portal:

Attributes for BBC:

The same attributes are released to each of the services above. These are, using the 'friendlyName's requested by BBC:

  • FirstName := givenName from UA AD
  • LastName := sn from UA AD
  • ContactRefCode := uaidentifier (aka Banner ID# or "30 million number") from UA AD
  • LogoutURL := static value for all users,

Additional documentation:

Step-by-step: Shibboleth authN to Bb Connect

Shibboleth wiki IdPUnsolicitedSSO

SAML 2 Technical Overview see §5.1.4

BBC Portal SSO overview (attachment)

see xml fragments from IdP config files in the attachments