Document ID: chunk:federal_register_of_legislation:F2024L01443:schedule:3:p2
Version: federal_register_of_legislation:F2024L01443
Segment Type: schedule
Provision Reference: sch 3 (pt 2/21)
Character Range: 242648–246205

time format.
Attributes               A collection of key-value pairs describing the Business Authorisation.                                                                                       A collection of objects with only 2 fields – name and value.

                                                                                                                                                                                      An enumeration of these values is defined by RAM.
Roles                    A list of literal values that define the roles an individual can assume on behalf of the entity.                                                             A collection of literals defined by RAM.
Entitlements             Additional privileges or permissions the individual may have when acting on behalf of the entity. The entitlements may be specific to a given PRP context.   A collection of literals defined by RAM or the service provider.
Attributes Last Updated  Date and time of when the authorisation was last modified.                                                                                                   RFC 3339 date and time in coordinated universal time format.

 Table 41 Business Authorisation entity type enumeraiton

Entity Type   Description                  Entity ID constraints
ABN           Australian Business Number   A numeric string of 11 characters in length.

    4.        OpenID Connect Attribute Profile

 To enable the use of attributes and attribute sets across the AGDIS an idiomatic mapping from this profile to Schedule 2 (AGDIS OpenID Connect Profile) is outlined in this Chapter.

 The mapping outlines requirements to ensure interoperability amongst entities participating in the AGDIS making and fulfilling attribute requests. The data types assigned to the mapped OIDC scopes and claims, for each attribute, are also defined here along with their representation.

    4.1   Attribute mapping

 This Schedule outlines 2 attribute mappings:

      1.             IXP to PRP; and
      2.             ISP to IXP.

 An IXP MUST implement support for the IXP relying party mapping (section 4.1.1 of this Schedule) for its PRPs.

 PRPs using OpenID Connect Core 1.0 as their federation protocol SHOULD use the IXP relying party mapping (section 4.1.1 of this Schedule) when configuring their service.

 An ISP MUST implement support for the ISP scopes and claims (section 4.1.2 of this Schedule) for its connected AGDIS IXPs.

 An IXP MUST support brokering attribute requests from the IXP relying party mapping to the ISP relying party mapping to support ISPs and PRPs using OpenID Connect Core 1.0 as their federation protocol (as outlined in Schedule 2 (AGDIS Open ID Connect Profile)).

      4.1.1      Identity Exchange Provider Relying Party Mapping

 The scopes an IXP MUST make available for a PRP to request are:

       * openid
       * profile
       * email
       * phone
       * tdif_other_names
       * tdif_docs
       * tdif_business_authorisations

 The attribute sets mapped to these OpenID Connect Core 1.0 scopes along with the relevant sets of claims is outlined in Table 42 below. A detailed attribute mapping to claims, along with data types, is presented in Table 46 below.

 Additional scopes for Self-Asserted Attributes that an IXP SHOULD support brokering attribute requests for are:
       * adgis_address
       * agdis_other_email
       * agdis_other_phone
       * agdis_birth_place
       * agdis_personal_title

 The Self-Asserted Attributes are mapped