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

[API] Roles per OAuth2 app #838

Closed
jstanden opened this Issue Dec 21, 2018 · 1 comment

Comments

Projects
1 participant
@jstanden
Copy link
Owner

jstanden commented Dec 21, 2018

No description provided.

@jstanden jstanden created this issue from a note in 9.2 (In Development) Dec 21, 2018

@jstanden jstanden added this to the 9.1 milestone Dec 21, 2018

@jstanden

This comment has been minimized.

Copy link
Owner

jstanden commented Dec 21, 2018

Implemented in 9.1

@jstanden jstanden closed this Dec 21, 2018

9.2 automation moved this from In Development to Completed Dec 21, 2018

jstanden added a commit that referenced this issue Dec 28, 2018

* [API/OAuth2] When configuring OAuth2 Apps for use with the API, eac…
…h app may define (in YAML) its own 'scopes' to control the available API endpoints. Additionally, each endpoint may include allowed verbs (e.g. GET/POST/PUT/DELETE). This makes it easy to offer read-only scopes to applications that don't need to modify data (e.g. knowledgebase search). When creating credentials for a new OAuth App, a default scopes policy is provided.

Fixes #838
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment