ID Token algorithm support requirements are ambiguous

[CDR-API-Stream]

Description

In the translation of ID Token Algorithm Selection Considerations from the Register design to the CDS the requirement for each participant type are not clearly defined and adds confusion to the differing support requirements for each participant type.

• Data holders must support at a minimum, 1 algorithm for each claim.
• Data Recipients must support all the algorithms used in the ecosystem to ensure they can communicate with all Data Holders.

Clarification on this topic was provided 2 years ago: ConsumerDataStandardsAustralia/register#97

Area Affected

Client Registration > ID Token Algorithm Selection Considerations

Change Proposed

The CDS needs to be updated so these requirements are clear.

We don’t anticipate any FDOs for this change as this requirement is already being met in production, and would be considered a non-breaking change

[CDR-API-Stream]

This issue has been staged at: ConsumerDataStandardsAustralia/standards-staging#199