Merge pull request #220 from mulesoft/dhilipuppili-patch-1

glenn-rodgers-sf · web-flow · commit fef8e7e7e9ae · 2022-11-15T09:37:22.000-06:00
Update mule-oauth-provider-landing-page.adoc
diff --git 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:
 

Original file line number	Diff line number	Diff line change
`@@ -80,7 +80,7 @@ You can define scopes in three different places:`
`80`	`80`	* In the `/validate` validation endpoint, to enforce a particular subset of the previously defined scopes.
`81`	`81`	`* In the Mule OAuth 2.0 Access Token Enforcement policy, where you can enforce scopes by specifying a space-separated list.`
`82`	`82`	`+`
`83`		-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.
	`83`	+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.
`84`	`84`
`85`	`85`	`Example of using scopes in Mule 4.2.x or later:`
`86`	`86`