Skip to content

Commit 69ea20f

Browse files
committed
Make Client Credentials authentication example non-normative and add RFC7523 reference
1 parent 0458856 commit 69ea20f

1 file changed

Lines changed: 9 additions & 3 deletions

File tree

index.bs

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -449,9 +449,15 @@ non-interactive authentication for scripts, automated agents, and server-to-serv
449449
NOTE: Scripts and bots can also use Solid-OIDC without Client Credentials via the [refresh token
450450
flow](https://www.rfc-editor.org/rfc/rfc6749#section-1.5), when supported by the server.
451451

452-
When using the Client Credentials Grant, the Client authenticates with the OP using a `client_id` and `client_secret`
453-
pair previously obtained through client registration (either static or dynamic). The Client sends a token request to
454-
the OP's token endpoint with `grant_type=client_credentials` and the `webid` scope.
452+
*This section is non-normative*
453+
454+
<div class='example'>
455+
When using the Client Credentials Grant, a Client could authenticate with the OP using a `client_id`
456+
and `client_secret` pair previously obtained through client registration (either static or dynamic). The Client
457+
sends a token request to the OP's token endpoint with `grant_type=client_credentials` and the `webid` scope.
458+
</div>
459+
460+
NOTE: [[!RFC7523]] (Section 2.2) presents another way to handle authentication using JWTs.
455461

456462
## Token Instantiation ## {#client-credentials-token-instantiation}
457463

0 commit comments

Comments
 (0)