Templates

This content is linked to Location Parameters

In the templates you can apply customization on pages rendered by IDHub. You get the choice between loading a templating or to redirect to a predefined URL.

Select IDP – This is a redirect to the Select IDP Page

Password Login – This is a redirect to the Password Login Page

Duplicate Subject – This is a redirect to the Duplicate Subject Page

Authorisation Failed – This is a redirect to the Authorisation Failed Page

Error – This is a redirect to the Error Pages

Logout – This is a redirect to the Logout Page

Consent – This is a redirect to the Consent Page

Self Service – This is a redirect to the Self Service Page

Reset Password – This is a redirect to the Reset Password Page

Change Password – This is a redirect to the Change Password Page

Register – This is a redirect to the New User Registration Page

Possible error codes passed to the error page

ACCESS_DENIED

internal code: ACCESS_DENIED

Message: Access denied


ACCOUNT_BLOCKED

internal code: ACCOUNT_BLOCKED

Message: Account is blocked


AUTHN_FAILED

internal code: AUTHN_FAILED

Message: The responding provider was unable to successfully authenticate the principal.


CERTIFICATE_NOT_FOUND

internal code: CERTIFICATE_NOT_FOUND

Message: A required certificate was not found


INSTALL_NOT_OK

internal code: INSTALL_NOK

Message: Installation is not completed, complete installation and retry


INTERNAL_SERVER_ERROR

internal code: essageKeys.INTERNAL_SERVER_ERROR

Message: Internal server error


INVALID_ATTR_NAME_OR_VALUE

internal code: urn:oasis:names:tc:SAML:2.0:status:InvalidAttrNameOrValue

Message: Unexpected or invalid content was encountered within a <saml:Attribute> or <saml:AttributeValue> element.


INVALID_NAME_ID_POLICY

internal code: urn:oasis:names:tc:SAML:2.0:status:InvalidNameIDPolicy

Message: The responding provider cannot or will not support the requested name identifier policy.


INVALID_PARAMETERS

internal code: INVALID_PARAMETERS

Message: There are some parameters with invalid values in the request.


MESSAGE_VALIDATION_FAILED

internal code: MESSAGE_VALIDATION_FAILED

Message: The parsing of a third party message has failed.


MISSING_PARAMETERS

internal code: MISSING_PARAMETERS

Message: There are some parameters missing in the request.


NO_AUTHN_CONTEXT

internal code: NO_AUTHN_CONTEXT

Message: The specified authentication context requirements cannot be met by the responder.


NO_AVAILABLE_IDP

internal code: urn:oasis:names:tc:SAML:2.0:status:NoAvailableIDP

Message: Used by an intermediary to indicate that none of the supported identity provider <Loc> elements in an <IDPList> can be resolved or that none of the supported identity providers are available.


NO_AVAILABLE_IDP

internal code: NO_IDPS

Message: Used by an intermediary to indicate that none of the supported identity provider <Loc> elements in an <IDPList> can be resolved or that none of the supported identity providers are available.


NO_PASSIVE

internal code: urn:oasis:names:tc:SAML:2.0:status:NoPassive

Message: Indicates that the responding provider cannot authenticate the principal passively, as has been requested.


NO_PROXY_SP

internal code: NO_PROXY_SP

Message: No Gateway Service Provider found


NO_SUBJECT

internal code: SP_SUBJECT_NOT_FOUND

Message: There is no value present for the attribute used as subject for the Service Provider you are trying to access


NO_SUPPORTED_IDP

internal code: urn:oasis:names:tc:SAML:2.0:status:NoSupportedIDP

Message: Used by an intermediary to indicate that none of the identity providers in an <IDPList> are supported by the intermediary.


PROXY_COUNT_EXCEEDED

internal code: urn:oasis:names:tc:SAML:2.0:status:ProxyCountExceeded

Message: Indicates that a responding provider cannot authenticate the principal directly and is not permitted to proxy the request further.


REQUEST_DENIED

internal code: REQUEST_DENIED

Message: The SAML responder or SAML authority is able to process the request but has chosen not to respond. This status code MAY be used when there is concern about the security contents of the request message or the sequence of request messages received from a particular requester.


REQUEST_UNSUPPORTED

internal code: urn:oasis:names:tc:SAML:2.0:status:RequestUnsupported

Message: The SAML responder or SAML authority does not support the request.


REQUEST_VERSION_DEPRECATED

internal code: urn:oasis:names:tc:SAML:2.0:status:RequestVersionDeprecated

Message: The SAML responder cannot process any requests with the protocol version specified in the request.


REQUEST_VERSION_TOO_HIGH

internal code: urn:oasis:names:tc:SAML:2.0:status:RequestVersionTooHigh

Message: The SAML responder cannot process the request because the protocol version specified in the request message is a major upgrade from the highest protocol version supported by the responder.


REQUEST_VERSION_TOO_LOW

internal code: urn:oasis:names:tc:SAML:2.0:status:RequestVersionTooLow

Message: The SAML responder cannot process the request because the protocol version specified in the request message is too low.


RESOURCE_NOT_RECOGNIZED

internal code: urn:oasis:names:tc:SAML:2.0:status:ResourceNotRecognized

Message: The resource value provided in the request message is invalid or unrecognized.


TOO_MANY_RESPONSES

internal code: urn:oasis:names:tc:SAML:2.0:status:TooManyResponses

Message: The response message would contain more elements than the SAML responder is able to return.


UNKNOWN_ATTR_PROFILE

internal code: urn:oasis:names:tc:SAML:2.0:status:UnknownAttrProfile

Message: An entity that has no knowledge of a particular attribute profile has been presented with an attribute drawn from that profile.


UNKNOWN_PRINCIPAL

internal code: urn:oasis:names:tc:SAML:2.0:status:UnknownPrincipal

Message: The responding provider does not recognize the principal specified or implied by the request.


UNKNOWN_ARTIFACT_ISSUER

internal code: UNKNOWN_ARTIFACT_ISSUER

Message: The issuer of a SAML artifact response could not be identified.


UNKNOWN_SP

internal code: UNKNOWN_SP

Message: The Service provider that sent the message is not known to us.


UNSUPPORTED_BINDING

internal code: urn:oasis:names:tc:SAML:2.0:status:UnsupportedBinding

Message: The SAML responder cannot properly fulfill the request using the protocol binding specified in the request.


WRONG_AUTHENTICATION_METHOD

internal code: WRONG_AUTHENTICATION_METHOD

Message: There was a problem finding the authentication method


WRONG_USER

internal code: IDP_WRONG_USER

Message: Mismatch between logged on user and incoming user


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.