From 999c973dd416085962be5b7328111a8a1ebf41bd Mon Sep 17 00:00:00 2001 From: dhilipuppili Date: Thu, 26 Mar 2020 10:30:39 +1100 Subject: [PATCH] Update mule-oauth-provider-landing-page.adoc Modified this as it is incorrect. This has been confirmed with Fede Balbi and Nahuel from the API Gateway team. --- modules/ROOT/pages/mule-oauth-provider-landing-page.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/mule-oauth-provider-landing-page.adoc b/modules/ROOT/pages/mule-oauth-provider-landing-page.adoc index 469ae9939..063db2ddf 100644 --- a/modules/ROOT/pages/mule-oauth-provider-landing-page.adoc +++ b/modules/ROOT/pages/mule-oauth-provider-landing-page.adoc @@ -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: