From 2b66c3838c98f06185870592e7906ba8d062f126 Mon Sep 17 00:00:00 2001 From: Gary Cheung Date: Tue, 10 Feb 2026 18:54:49 -0800 Subject: [PATCH] [W-21231057] update link --- 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 c0ab9467..edbfdac5 100644 --- a/modules/ROOT/pages/mule-oauth-provider-landing-page.adoc +++ b/modules/ROOT/pages/mule-oauth-provider-landing-page.adoc @@ -63,7 +63,7 @@ image::mule-oauth-provider.png[height=150,width=250] === Implementing Scopes -The OAuth 2.0 https://tools.ietf.org/html/rfc6749#page-23[scopes] enable you to further limit access to a resource protected by OAuth. You can define words, such as `READ` and `WRITE`, or others specific to your organization, such as `CONTRACTOR`, `PUBLIC`, `EMPLOYEES_ONLY`, and so on. +The OAuth 2.0 https://datatracker.ietf.org/doc/html/rfc6749#page-23[scopes] enable you to further limit access to a resource protected by OAuth. You can define words, such as `READ` and `WRITE`, or others specific to your organization, such as `CONTRACTOR`, `PUBLIC`, `EMPLOYEES_ONLY`, and so on. You can define scopes in three different places: