Document ID: chunk:federal_register_of_legislation:F2024L01443:body:0:p14
Version: federal_register_of_legislation:F2024L01443
Segment Type: other
Provision Reference: 
Character Range: 49195–52247

MUST provide a user dashboard that allows an individual, for the digital ID used to create the individual's current authenticated session, to:

 1.             view their consumer history;
 2.             manage the express consent they have given; and
 3.             manage their ISP preferences.

 The user dashboard MUST only display information for services at or below the level of assurance for the current authenticated session.

 When a user dashboard is accessed, an IXP MAY re-authenticate the individual, even if the individual already has a current authenticated session.

2.4   Data requirements

2.4.1      Attribute requirements

 An IXP MUST support brokering all attributes as outlined in Schedule 3 (AGDIS Attribute Profile).

 An IXP MUST support the disclosure of all IXP managed or generated attributes as outlined in Schedule 3 (AGDIS Attribute Profile).

 An IXP MUST support requesting any ISP specific attributes outlined in Schedule 3 (AGDIS Attribute Profile) in an authentication request to an ISP.

2.4.2      Computed attributes

 For each of their supported federation protocols, an IXP MUST implement the following requirements in this section.

 An IXP MUST support the disclosure of computed attributes as described in Schedule 3 (AGDIS Attribute Profile).

 An IXP MAY source computed attributes from an ISP or an ASP.

 An IXP MAY define support for additional computed attributes derived from attributes available from its ISPs and ASPs.

 Any new computed attribute MUST NOT violate attribute sharing policies defined in Schedule 3 (AGDIS Attribute Profile).

2.4.3      Attribute sharing policy

 The IXP MUST only disclose an attribute or attribute set with PRPs in accordance with that attribute or attribute set's attribute sharing policy as defined in Schedule 3 (AGDIS Attribute Profile).

2.4.4      Data representation

 When disclosing IXP specific attributes, an IXP MUST use the data representation as prescribed in Schedule 3 (AGDIS Attribute Profile).

 An IXP MAY use the data representation, defined in Schedule 3 (AGDIS Attribute Profile), to validate attribute payloads received from ISPs and ASPs.

 An IXP MUST NOT alter payloads received from an ISP or ASP unless the relevant attribute sharing polices explicitly permit alteration to occur.

3.        Identity service provider

 This Chapter outlines the requirements that MUST be met by ISPs.

3.1   Technical integration requirements

3.1.1      Protocol requirements

 An ISP MUST implement the ISP requirements in Schedule 2 (AGDIS OpenID Connect Profile).

3.1.2      Identity resolution

 An ISP MAY generate GPIs as prescribed in section 1.2.1 of this Schedule.

 An ISP SHOULD generate pairwise identifiers as prescribed in section 1.2.2 of this Schedule.

 An identifier linking a digital ID to an IXP MUST only be used to map that one-to-one relationship. The identifier MUST NOT be shared by the IXP with any other service connected to the ISP.

3.1.3      Single sign on

 An ISP MAY support an SSO scheme operated