Skip to content

Commit 16e4fbb

Browse files
authored
Updated link text to be descriptive and removed please
1 parent 46dd0be commit 16e4fbb

File tree

4 files changed

+8
-8
lines changed
  • 13/umbraco-cms/reference/content-delivery-api
  • 15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api
  • 16/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api
  • 17/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api

4 files changed

+8
-8
lines changed

13/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ If you are not familiar with members in Umbraco, please read the [Members](https
1717
{% endhint %}
1818

1919
{% hint style="warning" %}
20-
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, please consider adding additional layers of security.
20+
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, consider adding additional layers of security.
2121

22-
You'll find more details in [this article](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication) from Microsoft.
22+
For more details, see [Microsoft’s guide on configuring OpenID Connect for web authentication](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication).
2323
{% endhint %}
2424

2525
## Member authorization

15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ If you are looking to achieve server-to-server access to protected content, plea
1919
{% endhint %}
2020

2121
{% hint style="warning" %}
22-
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, please consider adding additional layers of security.
22+
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, consider adding additional layers of security.
2323

24-
You'll find more details in [this article](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication) from Microsoft.
24+
For more details, see [Microsoft’s guide on configuring OpenID Connect for web authentication](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication).
2525
{% endhint %}
2626

2727
## Member authorization

16/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ If you are looking to achieve server-to-server access to protected content, plea
1919
{% endhint %}
2020

2121
{% hint style="warning" %}
22-
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, please consider adding additional layers of security.
22+
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, consider adding additional layers of security.
2323

24-
You'll find more details in [this article](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication) from Microsoft.
24+
For more details, see [Microsoft’s guide on configuring OpenID Connect for web authentication](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication).
2525
{% endhint %}
2626

2727
## Member authorization

17/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ Member authentication and authorization in the Delivery API is performed using t
2424
Most programming languages have OpenId Connect client libraries to handle the complexity for us. [`AppAuth`](https://appauth.io/) is a great example of such a library. In ASP.NET Core, OpenId Connect support is built into the framework.
2525

2626
{% hint style="warning" %}
27-
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, please consider adding additional layers of security.
27+
It is no longer recommended to use public OpenID Connect (OAuth) clients for web applications. If you want to use protected content from the Delivery API in a web application, consider adding additional layers of security.
2828

29-
You'll find more details in [this article](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication) from Microsoft.
29+
For more details, see [Microsoft’s guide on configuring OpenID Connect for web authentication](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/configure-oidc-web-authentication).
3030
{% endhint %}
3131

3232
### Enabling member authorization

0 commit comments

Comments
 (0)