Requirements

As an IdP

If you want to connect your institution to UNIFICAT, make sure it meets the following requirements beforehand:

1. The institution must have an identity provider interoperable through the SAML 2.0.
2. The institution must decide who the technical contact of the IdP is: name, surname and e-mail.
3. The institution must decide who the administrative contact of the IdP is: name, surname and e-mail. 
4. The institution must provide the name and logo with which the identity provider will be displayed in the federation.
5. The institution must have all IdP metadata available in a URL under HTTPS protocol, in which the web server uses an EV digital certificate to clearly identify the institution.
6. The IdP of the institution must fulfill the technical requirements of the federation, and especially: 
7. a) It must include the HUB metadata of the federation as a service provider on both environments (validation and production).
   b) It must issue attributes of their users to both service providers as indicated on the federation attribute policy.

For more information, see the technical requirements document (in Spanish)!

As an SP

If you want to connect a service to UNIFICAT, make sure it meets the following requirements beforehand:

1. The organization must facilitate the service provider to interoperate with UNIFICAT through one of the following protocols: SAML 1.1/2.0 Shibboleth 1.3, PAPI, CAS, OAuth 2 or OpenID Connect, with SAML 2.0 currently being the recommendation.
2. The organization must have service provider metadata available at a URL under HTTP protocol.
3. The organization must meet the technical requirements of the federation, and especially:
   a) It must include the HUB metadata of the federation as a service provider on both environments (validation and production), available in http://...
   b) The organization must provide a list of the attributes they wish to receive from the federation based on those listed in the federation's attribute issue policy (if they are not included in the service provider's metadata).

For more information, see the technical requirements document (in Spanish)!