OB Solution Supported Token Endpoint Auth Methods are not Mentioned in the Documentation

[KasuniHemasika]

Description:

According to the specification in [1], the FAPI compliant token_endpoint_auth_method values for the DCR registration request are tls_client_auth and private_key_jwt.

Guess this should be added as a note to the documentation in [2],[3] & [4] saying that we are only supporting these two FAPI compliant methods.

[1] - https://openbanking.atlassian.net/wiki/spaces/DZ/pages/1078034771/Dynamic+Client+Registration+-+v3.2#DynamicClientRegistration-v3.2-DataDictionary [2] - https://docs.wso2.com/display/OB140/Dynamic+Client+Registration+v3.2#DynamicClientRegistrationv3.2-Registeringanapplication [3] - https://docs.wso2.com/display/OB150/Dynamic+Client+Registration+v3.2#DynamicClientRegistrationv3.2-Registeringanapplication [4] - https://docs.wso2.com/display/OB130/Dynamic+Client+Registration+v3.2#DynamicClientRegistrationv3.2-Registeringanapplication

Suggested Labels:

Suggested Assignees:

Affected Product Version: OB 1.3.0,1.4.0,1.5.0

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

[isharailanga]

Hi Kasuni,

Updated all DCR v3.2 pages with a note mentioning the $subject. Please review and close the issue.

[KasuniHemasika]

Hi Ishara,

Reviewed the change and it is as expected. Thank you. Will close the issue.