Skip to content

Update mule-oauth-provider-landing-page.adoc #220

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.

Sign up for GitHub

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

Merged
glenn-rodgers-sf merged 2 commits into from
Nov 15, 2022
Merged

Update mule-oauth-provider-landing-page.adoc #220

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
999c973
Update mule-oauth-provider-landing-page.adoc
dhilipuppili Mar 25, 2020
bef7473
Merge branch 'v2.x' into dhilipuppili-patch-1
glenn-rodgers-sf Nov 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/ROOT/pages/mule-oauth-provider-landing-page.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ You can define scopes in three different places:
* In the `/validate` validation endpoint, to enforce a particular subset of the previously defined scopes.
* In the Mule OAuth 2.0 Access Token Enforcement policy, where you can enforce scopes by specifying a space-separated list.
+
Specifying more than one scope enforces the `OR` logic. If the token to be validated is associated with at least one of the requested scopes, the policy validates the token successfully.
Specifying more than one scope enforces the `AND` logic. If the token to be validated is associated with all of the requested scopes, the policy validates the token successfully.

Example of using scopes in Mule 4.2.x or later:

Expand Down