
Renater provides an SAML federation for higher education in France.
It is based on SAMLv2 but add some specific items like a WAYF service and a metadata bundle to list all SP and IDP from the federation.
If you want to give access to applications protected with LL::NG to users of the federation then you will act as a Service Provider.
Configure LL::NG as SAML Service Provider with this documentation. You don’t need to declare any IDP for the moment.
Configure SAML Discovery Protocol to redirect users on WAYF Service. The endpoint URL is https://discovery.renater.fr/renater/WAYF.
With configuration CLI:
/usr/*/lemonldap-ng/bin/lemonldap-ng-cli set \
samlDiscoveryProtocolActivation 1 \
samlDiscoveryProtocolURL https://discovery.renater.fr/renater/WAYF.
Follow SAML Federation documentation to enable IDP metadata file bundle download as a cronjob. For example, in /etc/cron.d/metadata-download file:
30 3 * * * root /usr/share/lemonldap-ng/bin/downloadSamlMetadata -m https://pub.federation.renater.fr/metadata/renater/main/main-idps-renater-metadata.xml -o /etc/lemonldap-ng/metadata/main-idps-renater-metadata.xml
Then declare this file in SAML2 Service > Advanced > Federation > SAML Federation Metadata files.
With configuration CLI:
/usr/*/lemonldap-ng/bin/lemonldap-ng-cli set \
samlFederationFiles /etc/lemonldap-ng/metadata/main-idps-renater-metadata.xml
Go to Renater registration portal and register your SP on the Renater federation.
Attention
Be sure to check all attributes as mandatory to be able to get them in SAML assertions. Remember OID and name ti configure them in LL::NG.
Declare a template Identity Provider in LL::NG configuration that will hold the default settings for all IDP of the Renater Federation :
With configuration CLI:
/usr/*/lemonldap-ng/bin/lemonldap-ng-cli addKey \
samlIDPMetaDataExportedAttributes/idp-renater mail '0;urn:oid:0.9.2342.19200300.100.1.3;urn:oasis:names:tc:SAML:2.0:attrname-format:uri;mail' \
samlIDPMetaDataExportedAttributes/idp-renater uid '0;urn:oid:1.3.6.1.4.1.5923.1.1.1.6;urn:oasis:names:tc:SAML:2.0:attrname-format:uri;eduPersonPrincipalName' \
samlIDPMetaDataOptions/idp-renater samlIDPMetaDataOptionsFederationEntityID 'https://federation.renater.fr/' \
samlIDPMetaDataOptions/idp-renater samlIDPMetaDataOptionsNameIDFormat 'unspecified'
Tip
You can override these settings for a specific IDP by creating a new IDP in configuration and configuring the Federation EntityID with the value of the IDP EntityID.
If you want to give access to Renater applications (SP) to users authenticated with your LL::NG server, then you will act as an Identity Provider.
Configure LL::NG as SAML Identity Provider with this documentation. You don’t need to declare any SP for the moment.
Attention
If your LL::NG server will act as SP and IDP inside Renater federation, you need to set the advanced parameter “Override Entity ID for IDP”. Indeed, Renater do not allow to register a SP and an IDP with the same entityID.
Follow SAML Federation documentation to enable SP metadata file bundle download as a cronjob. For example, in /etc/cron.d/metadata-download file:
30 2 * * * root /usr/share/lemonldap-ng/bin/downloadSamlMetadata -m https://pub.federation.renater.fr/metadata/renater/main/main-sps-renater-metadata.xml -o /etc/lemonldap-ng/metadata/main-sps-renater-metadata.xml
Then declare this file in SAML2 Service > Advanced > Federation > SAML Federation Metadata files.
With configuration CLI:
/usr/*/lemonldap-ng/bin/lemonldap-ng-cli set \
samlFederationFiles /etc/lemonldap-ng/metadata/main-sps-renater-metadata.xml
Go to Renater registration portal and register your IDP on the Renater federation.
Declare a template Service Provider in LL::NG configuration that will hold the default settings for all SP of the Renater Federation:
With configuration CLI:
/usr/*/lemonldap-ng/bin/lemonldap-ng-cli addKey \
samlSPMetaDataOptions/sp-renater samlSPMetaDataOptionsFederationEntityID 'https://federation.renater.fr/' \
samlSPMetaDataOptions/sp-renater samlSPMetaDataOptionsFederationRequiredAttributes'optional'
Tip
You can override these settings for a specific SP by creating a new SP in configuration and configuring the Federation EntityID with the value of the SP EntityID.