Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add clientAuthorizationType property to Security Scheme Object #785

Closed
MugeSo opened this issue Sep 10, 2016 · 1 comment
Closed

Add clientAuthorizationType property to Security Scheme Object #785

MugeSo opened this issue Sep 10, 2016 · 1 comment

Comments

@MugeSo
Copy link

MugeSo commented Sep 10, 2016

Background

RFC6749 allows authorization server to implement client authentication, which is used when a credential client access to token endpoint.

If the client type is confidential, the client and authorization
server establish a client authentication method suitable for the
security requirements of the authorization server. The authorization
server MAY accept any form of client authentication meeting its
security requirements.

RFC6749 also describes 2 typical client authentication method in §2.3.1.
However it allows any other suitable HTTP authentication scheme in §2.3.2

Proposal

To follow this spec, I propose to add a `clientAuthorizationType' property to Security Scheme Object.

OR

Add clientAuthorization property which is an Object like Security Scheme Object.

@lornajane
Copy link
Contributor

Since this issue hasn't had much interaction or engagement, it will be closed.

@lornajane lornajane closed this as not planned Won't fix, can't repro, duplicate, stale Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants