AAI FAQ

From EGIWiki
Jump to: navigation, search

Contents


AAI and CheckIn FAQ

IdP and user questions

Connect to CheckIn an IdP federated in an hub and spoke federations

Question: I get an error similar to: "Error - No connection between institution and service" (SURFconext example)

Answer:

In case of a "hub and spoke" federation the federation coordinator may require that the IdP administrators explicitly request to connect to a SP and let their users to authenticate on these SP.

In most of the cases this is not a configuration problem neither for the CheckIn service nor for the Identity provider. The connection needs to be implemented in the hub and spoke IdP Proxy.

One example of such federation is SURFconext, the national IdP federation for research and education in the Netherlands operated by SURFnet. If you are using credentials from a Dutch IdP in eduGAIN, you or your IdP administrators need to request the connection. The following steps will lead you to perform the connection:

Authentication error with ADFS-based Identity Providers

Question: Why do I get the error below after successfully authenticating at my Home IdP?

opensaml::FatalProfileException at (https://aai.egi.eu/registry.sso/SAML2/POST)
SAML response reported an IdP error.
Error from identity provider:
Status: urn:oasis:names:tc:SAML:2.0:status:Responder

Answer:

The Responder error status is typically returned from ADFS-based IdP implementations (notably Microsoft ADFS 2.0 and ADFS 3.0) that cannot properly handle Scoping elements (see https://docs.microsoft.com/en-za/azure/active-directory/develop/active-directory-single-sign-on-protocol-reference#scoping). CheckIn can be configured to omit the scoping element from the authentication requests sent to such IdPs in order to allow successful logins. Please contact the CheckIn support team and include a screenshot of your error.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export