AAI guide for IdPs

From EGIWiki
Jump to: navigation, search



This wiki page contains information about integrating your identity provider with the EGI AAI Proxy in order to allow users in your community to access EGI tools and services.

Organisations who want to register their IDP in CheckIn needs to fill this form in case the IdP is not publishing RnS and Sirtfi compliance in eduGAIN. A PDF scansion of a printed and signed copy should be sent to operations [at] egi.eu

SAML Identity Provider

To allow users in your community to sign into federated EGI applications, you need to connect to the EGI AAI SP Proxy as a SAML Identity Provider (IdP). Users of the application will be redirected to the central Discovery Service page of the EGI AAI Proxy where they will able to select to authenticate at your IdP. Once the user is authenticated, the EGI AAI Proxy will return a SAML assertion to the application containing the information returned by your IdP about the authenticated user.

Metadata registration

SAML authentication relies on the use of metadata. Both parties (you as an IdP and the EGI AAI SP) need to exchange metadata in order to know and trust each other. The metadata include information such as the location of the service endpoints that need to be invoked, as well as the certificates that will be used to sign SAML messages. The format of the exchanged metadata should be based on the XML-based SAML 2.0 specification. Usually, you will not need to manually create such an XML document, as this is automatically generated by all major SAML 2.0 IdP software solutions (e.g., Shibboleth, SimpleSAMLphp). It is important that you serve your metadata over HTTPS using a browser-friendly SSL certificate, i.e. issued by a trusted certificate authority.

To exchange metadata, please send an email including the following information:

  1. entityID
  2. Metadata URL

Depending on the software you are using, the authoritative XML metadata URL for your IdP might be in the following form:

Note that if your IdP is part of a federation, then it would be preferred to send us the URL to a signed federation metadata aggregate. We can then cherry pick the appropriate entityID from that.

You can get the metadata of the EGI SP Proxy from the following URL: https://aai.egi.eu/proxy/module.php/saml/sp/metadata.php/sso

Alternatively, you can use one of the following signed metadata aggregates:

Attribute release

Within the EGI environment, a user must have one persistent, non-reassignable, non-targeted, opaque, and globally unique identifier. To achieve this, the EGI AAI Proxy generates a eduPersonUniqueId (urn:oid: attribute based on the first non-empty value from this attribute list:

As such, it is required by your IdP to release at least one of the above user identifiers.

The selected attribute value is hashed and the "egi.eu" scope portion is added to the generated ePUID, e.g.:


The generated ePUID should be accompanied with a minimum set of attributes:

The EGI AAI SP Proxy will attempt to retrieve these attributes from your IdP. If this is not possible, the missing user attributes will be acquired and verified through the user registration process with the EGI Account Registry .

Note that the above set of request attributes complies with the REFEDS R&S attribute bundle.

A more extensive list of all the attributes that may be made available to Service Providers is included in the following table:

Attribute friendly name Attribute OID Example value
eduPersonUniqueId urn:oid: ef72285491ffe53c39b75bdcef46689f5d26ddfa00312365cc4fb5ce97e9ca87@egi.eu
mail urn:oid:0.9.2342.19200300.100.1.3 john.doe@example.org
displayName urn:oid:2.16.840.1.113730.3.1.241 John Doe
givenName urn:oid: John
sn urn:oid: Doe
eduPersonAssurance urn:oid: https://aai.egi.eu/LoA#Substantial
distinguishedName urn:oid: /C=NL/O=Example.org/CN=John Doe
eduPersonScopedAffiliation urn:oid: faculty@example.org
eduPersonEntitlement urn:oid: urn:mace:egi.eu:www.egi.eu:wiki-editors:member@egi.eu

Integration success stories

Personal tools