Editorial: Language describing acceptable token endpoint authentication mechanisms.

[Ralph Bragg]

Given that one describes a specific mechanism support by name shouldn’t for consistency this read

1. tls_client_auth or self_signed_tls_client_auth as specified in section 2 of MTLS. Also is private_key_jwt meant to be in grey?

shall authenticate the confidential client using one of the following methods (this overrides FAPI part 1 clause 5.2.2.4):

1. Mutual TLS for OAuth Client Authentication as specified in section 2 of MTLS;
2. private_key_jwt as specified in section 9 of OIDC;

‌

[Nat Sakimura]

fixes #321 - Editorial: Language describing acceptable token endpoint authentication mechanisms

→ <<cset 9121ca1e8b20>>

[Nat Sakimura]

Merged in issue_321 (pull request #199)

fixes #321 - Editorial: Language describing acceptable token endpoint authentication mechanisms

Approved-by: Dave Tonge Approved-by: Stuart Low Approved-by: Nat Sakimura Approved-by: Joseph Heenan Approved-by: Daniel Fett

→ <<cset 8fb45d1189d6>>