Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

OAuth 2.0 grant type naming missmatch #159

Open
G-2-Z opened this issue Mar 19, 2018 · 2 comments
Open

OAuth 2.0 grant type naming missmatch #159

G-2-Z opened this issue Mar 19, 2018 · 2 comments

Comments

@G-2-Z
Copy link

G-2-Z commented Mar 19, 2018

The grant types supported by Osprey security:

[code, token, owner, credentials]

are not the official OAuth 2.0 grant types and also not valid RAML 1.0:

[authorization_code, password, client_credentials, implicit]

@jstoiko
Copy link
Contributor

jstoiko commented Apr 3, 2018

It seems like you are right. This may be something inherited from RAML 0.8 that was changed in 1.0 [1]. @G-2-Z: are you interested in submitting a PR for this?

[1] https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md/#oauth-20

@G-2-Z
Copy link
Author

G-2-Z commented Apr 5, 2018

Not right now, but i might have to work on it the next weeks. If i find the time to make it generic i will submit one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants