Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Abstract

...

This document is a product of the Universal Login Experience Work Group. It records the requirements for the user experience based on scenarios and use cases.

...

Status

...

This document is currently under active development. Its latest version can always be found here. See the Change History at the end of this document for its revision number.

...

Editors

...

  • TBD

...

Intellectual Property Notice

...

The Universal Login Experience Work Group operates under Option Liberty and the publication of this document is governed by the policies outlined in this option.

...

Table of Contents
minLevel1
maxLevel3
outlinetrue
indent20px

...

Overview

This is a summary of the collective set of information supplied by all of the actors (IdP, RP, User Agent) in constructing a suitable pop-up experience for discovery.

...

Relying Party Inputs

  • Required/Optional Claims
    • Required and optional identifier/attribute information needed to proceed with login and "immediately expected" user activity.

...

  • UI Information
    • Properties to influence UI (colors, fonts, ...)

...

Identity Provider Inputs

  • Supported Claims
    • Identifier/attribute information offered

...

  • Registration/Credentialing Bootstrap
    • Link to location(s) to help users acquire the necessary credential (e.g. an Infocard)

Supported claims

IDP's supported attributes and claims

SAML

Already defined in SAML Metadata specifications

...

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