Document ID: chunk:federal_register_of_legislation:F2024L01443:body:0:p13
Version: federal_register_of_legislation:F2024L01443
Segment Type: other
Provision Reference: 
Character Range: 46671–49480

IXP MUST facilitate gathering those attributes from the ASP.

 An IXP MUST implement mechanisms to support the access channels it has agreed with an ASP as referenced in section 4.1.2 of this Schedule.

 When accessing attributes directly from the ASP, an IXP MUST do so using the pairwise identifier it has issued to the ASP.

 To facilitate direct communication between an ASP and a PRP, an IXP MAY share an individual's encrypted pairwise identifier:

(a)            for the ASP with the PRP requesting authentication; and
(b)            for the PRP with the ASP that can fulfill the attribute requests.

 If an IXP chooses to share an encrypted identifier, the identifier MUST be:

      1.             encrypted using a public key of the PRP or ASP it belongs to; and
      2.             be packaged with a timestamp and a nonce to limit the opportunity for replay and the creation of de facto pairwise identifiers.

2.1.9      Federation protocol brokering

 When accepting authentication requests from a PRP, an IXP MUST broker the federation protocol used by the PRP to the federation protocol of the ISP selected by the individual.

2.2   Identity provider selection

 An IXP MUST provide a mechanism for the individual to choose an ISP.

 The list of ISPs presented by an IXP MUST only display ISPs that satisfy the IP level and AL requested in the PRP's authentication request.

 An IXP MAY provide a mechanism for the individual to remember their choice of ISP for a given PRP.

 If an individual has remembered their ISP choice for a given PRP, an IXP MAY redirect them to the remembered ISP.

 If an IXP provides a mechanism to remember ISP selection, the IXP MUST provide:

 1.             a notice to ensure the individual understands the nature of the express consent they are providing;
 2.             a notice outlining the duration of the remembered ISP selection and the limitations on how it is remembered (for example, if it is limited to the device or web browser from which the express consent is given); and
      3.             a mechanism to revoke the remembered choice.

2.2.1      Blinding

 An IXP MUST NOT broker any information about the PRP requesting authentication to any of its ISPs.

 An IXP MAY inform the PRP which ISP the individual used to authenticate.

 If an IXP informs the PRP which ISP the individual used to authenticate, the IXP MUST do so in accordance with the requirements outlined for the federation protocol used by the PRP.

2.3   User dashboard

 An IXP 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