...
- Registration/Credentialing Bootstrap
- Link to location(s) to help users acquire the necessary credential (e.g. an Infocard)
User Agent Inputs
- Preferred/Supported/Previously Used Issuers
- Opportunity to bias or pre-populate choices based on history, user affiliations/preferences, etc.
- Accessibility Requirements
- Do pop-ups cause accessibility concerns for discovery or login?
See Also
...
Supported claims
IDP's supported attributes and claims
SAML
Already defined in SAML Metadata specifications
Example :
| Code Block |
|---|
<IDPSSODescriptor WantAuthnRequestsSigned="true"
protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
...
<saml:Attribute
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"
Name="urn:saml_attribute_name_1" />
<saml:Attribute
NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"
Name="urn:saml_attribute_name_2" />
...
</IDPSSODescriptor>
|
OpenID
- The Yadis XRDS document only advertizes the SREG/AX service(s) supported by the OP but not the exact list of supported attributes/claims.
- Proposal : Extension to the YADIS XRDS document.
Explicitly advertize OP's supported attributes/claims part of XRDS document published by the OP ?
_Help needed on best way to do it with XRDS