You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/server-to-server-access.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,17 +4,17 @@ description: How to fetch protected content from the Delivery API with a server-
4
4
5
5
# Server-to-server access to protected content in the Delivery API
6
6
7
-
If protected content is consumed from Delivery API in a server-to-server context, the [interactive authorization flow](README.md) won't work. Instead, we have to utilise the OpenId Connect Client Credentials flow, which is configured in the application settings.
7
+
If protected content is consumed from the Delivery API in a server-to-server context, the [interactive authorization flow](README.md) won't work. Instead, we have to utilize the OpenId Connect Client Credentials flow, which is configured in the application settings.
8
8
9
9
## Configuration
10
10
11
-
In the Delivery API, Client Credentials work by mapping known Members to client IDs and secrets. These Members are known as API Members. When an API consumer uses the Client Credentials of an API Member, the consumer efficiently assumes the identity of this API Member.
11
+
In the Delivery API, Client Credentials map known Members to client IDs and secrets. These Members are known as API Members. When an API consumer uses the Client Credentials of an API Member, the consumer efficiently assumes the identity of this API Member.
12
12
13
13
{% hint style="info" %}
14
-
An API Member works exactly the same as a regular Member, with the added option of authorizing with Client Credentials.
14
+
An API Member works the same as a regular Member, with the added option of authorizing with Client Credentials.
15
15
{% endhint %}
16
16
17
-
In the following configuration example, the Member "member@local" are mapped to a set of Client Credentials:
17
+
In the following configuration example, the Member "member@local" is mapped to a set of Client Credentials:
18
18
19
19
{% code title="appsettings.json" %}
20
20
@@ -44,7 +44,7 @@ In the following configuration example, the Member "member@local" are mapped to
44
44
45
45
{% endcode %}
46
46
47
-
After restarting the site, the backoffice will now list "member@local" as an API Member:
47
+
After restarting the site, the backoffice will list "member@local" as an API Member:
48
48
49
49

0 commit comments