Fix namespaces for IdentityModel.

Author: khalidabuhakmeh

src/content/docs/identityserver/quickstarts/1-client-credentials.md

@@ -380,9 +380,9 @@ endpoint addresses can be read from the metadata. Add the following to the
 client's Program.cs in the `src/Client/Program.cs` directory:
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
-// discover endpoints from metadata
+// discovery endpoints from metadata
 var client = new HttpClient();
 var disco = await client.GetDiscoveryDocumentAsync("https://localhost:5001");
 if (disco.IsError)

src/content/docs/identityserver/reference/endpoints/ciba.md

@@ -83,7 +83,7 @@ required to implement the `IBackchannelAuthenticationUserValidator` interface.
 
   instead of providing all parameters as individual parameters, you can provide all them as a JWT
 
-```text
+```http request
 POST /connect/ciba
 
     client_id=client1&
@@ -94,7 +94,7 @@ POST /connect/ciba
 
 And a successful response will look something like:
 
-```text
+```http request
 HTTP/1.1 200 OK
 Content-Type: application/json
 Cache-Control: no-store
@@ -108,11 +108,11 @@ Cache-Control: no-store
 
 ## .NET Client Library
 
-You can use the [Duende IdentityModel](../../../identitymodel) client library to programmatically interact with
+You can use the [Duende IdentityModel](/identitymodel/index.mdx) client library to programmatically interact with
 the protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 

src/content/docs/identityserver/reference/endpoints/device-authorization.md

@@ -36,11 +36,11 @@ POST /connect/deviceauthorization
 
 ## .NET Client Library
 
-You can use the [Duende IdentityModel](../../../identitymodel) client library to programmatically interact with
+You can use the [Duende IdentityModel](/identitymodel/index.mdx) client library to programmatically interact with
 the protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 

src/content/docs/identityserver/reference/endpoints/introspection.md

@@ -55,11 +55,11 @@ An invalid request will return a 400, an unauthorized request 401.
 
 ## .NET Client Library
 
-You can use the [Duende IdentityModel](../../../identitymodel) client library to programmatically interact with
+You can use the [Duende IdentityModel](/identitymodel/index.mdx) client library to programmatically interact with
 the protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 

src/content/docs/identityserver/reference/endpoints/revocation.md

@@ -33,11 +33,11 @@ token=...&token_type_hint=refresh_token
 
 ## .NET Client Library
 
-You can use the [Duende IdentityModel](../../../identitymodel) client library to programmatically interact with
+You can use the [Duende IdentityModel](/identitymodel/index.mdx) client library to programmatically interact with
 the protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 

src/content/docs/identityserver/reference/endpoints/token.md

@@ -100,11 +100,11 @@ CONTENT-TYPE application/x-www-form-urlencoded
 
 ## .NET Client Library
 
-You can use the [Duende IdentityModel](../../../identitymodel) client library to programmatically interact with
+You can use the [Duende IdentityModel](/identitymodel/index.mdx) client library to programmatically interact with
 the protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 

src/content/docs/identityserver/reference/endpoints/userinfo.md

@@ -37,17 +37,31 @@ Content-Type: application/json
 
 ## .NET Client Library
 
-You can use the [Duende IdentityModel](../../../identitymodel) client library to programmatically interact with
+You can use the [Duende IdentityModel](/identitymodel/index.mdx) client library to programmatically interact with
 the protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 
-var response = await client.GetUserInfoAsync(new UserInfoRequest
+var disco = await client.GetDiscoveryDocumentAsync("https://localhost:5001");
+
+var token = await client.RequestAuthorizationCodeTokenAsync(new AuthorizationCodeTokenRequest
+{
+    Address = disco.TokenEndpoint,
+
+    ClientId = "client",
+    ClientSecret = "secret",
+
+    Code = "...",
+    CodeVerifier = "...",
+    RedirectUri = "https://app.com/callback"
+});
+
+var userInfo = await client.GetUserInfoAsync(new UserInfoRequest
 {
     Address = disco.UserInfoEndpoint,
-    Token = token
+    Token = token.AccessToken
 });
 ```

src/content/docs/identityserver/tokens/client-authentication.md

@@ -86,7 +86,7 @@ The following secret parsers are part of Duende IdentityServer:
 
 
 ### Secret Validation
-It is the job of implementations of the [ISecretValidator](/identityserver/reference/models/secrets#duendeidentityservermodelparsedsecret) interface to validate the extracted credentials.
+It is the job of implementations of the [ISecretValidator](/identityserver/reference/models/secrets.md#duendeidentityservermodelparsedsecret) interface to validate the extracted credentials.
 
 You can add secret validators by calling the `AddSecretValidator()` service provider extension method.
 
@@ -154,7 +154,7 @@ var compromisedSecret = new Secret("just for demos, not prod!".Sha256());
 
 You can either send the client id/secret combination as part of the POST body::
 
-```
+```http request
 POST /connect/token
 
 Content-type: application/x-www-form-urlencoded
@@ -169,7 +169,7 @@ Content-type: application/x-www-form-urlencoded
 
 ...or as a basic authentication header::
 
-```
+```http request
 POST /connect/token
 
 Content-type: application/x-www-form-urlencoded
@@ -182,11 +182,11 @@ Authorization: Basic xxxxx
 
 ### .NET Client Library
 
-You can use the [Duende IdentityModel](../../../identitymodel) client library to programmatically interact with
+You can use the [Duende IdentityModel](/identitymodel/index.mdx) client library to programmatically interact with
 the protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 
@@ -253,7 +253,7 @@ You can share the same key for client authentication and [signed authorize reque
 
 On the client side, the caller must first generate the JWT, and then send it on the `assertion` body field:
 
-```
+```http request
 POST /connect/token
 
 Content-type: application/x-www-form-urlencoded
@@ -299,7 +299,7 @@ private static string CreateClientToken(SigningCredentials credential, string cl
 protocol endpoint from .NET code.
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 static async Task<TokenResponse> RequestTokenAsync(SigningCredentials credential)
 {

src/content/docs/identityserver/tokens/refresh.md

@@ -17,7 +17,7 @@ access token. This can be done with an API call and does not require any user in
 
 Since this is a privileged operation, the clients needs to be explicitly authorized to be able to use refresh tokens by
 setting the `AllowOfflineAccess` property to `true`. See
-the [client reference](/identityserver/reference/models/client#refresh-token) section for additional refresh token
+the [client reference](/identityserver/reference/models/client.md#refresh-token) section for additional refresh token
 related settings.
 
 Refresh tokens are supported for the following flows: authorization code, hybrid and resource owner password credential
@@ -45,11 +45,11 @@ POST /connect/token
 
 #### .NET Client Library
 
-On .NET you can leverage the [Duende IdentityModel](../../../identitymodel) client library
-to [request](../../../identitymodel/endpoints/token) refresh tokens, e.g.:
+On .NET you can leverage the [Duende IdentityModel](/identitymodel/index.mdx) client library
+to [request](/identitymodel/endpoints/token.md) refresh tokens, e.g.:
 
 ```cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 
@@ -77,7 +77,7 @@ are issued to and the client is required to authenticate itself in order to do s
 token issued to a confidential client cannot use it without the client's credentials.
 
 Refresh tokens issued to public clients are not bound to the client in the same way, since the client cannot
-authenticate itself. We recommend that such refresh tokens be sender-constrained using [Proof of Possession](/identityserver/tokens/pop/)
+authenticate itself. We recommend that such refresh tokens be sender-constrained using [Proof of Possession](/identityserver/tokens/pop.md)
 instead.
 
 You can further reduce the attack surface of refresh tokens using the following techniques.
@@ -124,7 +124,7 @@ to produce a new token, but the response containing the new refresh token is los
 application has no way to recover without the user logging in again. Reusable refresh tokens do not have this problem.
 
 Reusable tokens may have better performance in
-the [persisted grants store](/identityserver/reference/stores/persisted-grant-store/). One-time use refresh tokens
+the [persisted grants store](/identityserver/reference/stores/persisted-grant-store.md). One-time use refresh tokens
 require additional records to be written to the store whenever a token is refreshed. Using reusable refresh tokens
 avoids those writes.
 
@@ -175,4 +175,4 @@ replay detection. The `PersistentGrantOptions.DeleteOneTimeOnlyRefreshTokensOnUs
 used tokens persist and can be used to detect replays. The cleanup job should also be configured to not delete consumed
 tokens.
 
-See also: The [IRefreshTokenService](/identityserver/reference/services/refresh-token-service/) reference.
+See also: The [IRefreshTokenService](/identityserver/reference/services/refresh-token-service.md) reference.

src/content/docs/identityserver/tokens/requesting.md

@@ -12,7 +12,7 @@ redirect_from:
 ---
 
 A typical architecture is composed of two application (aka
-client) [types](/identityserver/overview/terminology#client) - machine-to-machine calls and interactive applications.
+client) [types](/identityserver/overview/terminology.md#client) - machine-to-machine calls and interactive applications.
 
 ## Machine-to-machine Communication
 
@@ -21,9 +21,9 @@ API.
 
 Prerequisites are:
 
-* define a [client](/identityserver/fundamentals/clients) for the *client credentials* grant type
-* define an [API scope](/identityserver/fundamentals/resources/api-scopes/) (and optionally a resource)
-* grant the client access to the scope via the [`AllowedScopes`](/identityserver/reference/models/client#basics)
+* define a [client](/identityserver/fundamentals/clients.md) for the *client credentials* grant type
+* define an [API scope](/identityserver/fundamentals/resources/api-scopes.md) (and optionally a resource)
+* grant the client access to the scope via the [`AllowedScopes`](/identityserver/reference/models/client.md#basics)
   property
 
 According to the OAuth [specification](https://tools.ietf.org/html/rfc6749#section-4.4), you request a token by posting
@@ -63,7 +63,7 @@ The above token request would look like this in C#:
 
 ```csharp
 // Program.cs
-using IdentityModel.Client;
+using Duende.IdentityModel.Client;
 
 var client = new HttpClient();
 
@@ -208,7 +208,7 @@ Pragma: no-cache
 ```
 
 :::note
-See the refresh token section for more information on how to deal with [refresh tokens](/identityserver/tokens/refresh).
+See the refresh token section for more information on how to deal with [refresh tokens](/identityserver/tokens/refresh.md).
 :::
 
 ### .NET Client Library