Merge pull request #980 from DuendeSoftware/mb/bulk

Update code snippets to use consistent `csharp` syntax highlighting across IdentityServer documentation.

Author: maartenba

src/content/docs/accesstokenmanagement/advanced/client-credentials.mdx

@@ -318,7 +318,7 @@ The client registration object has two additional properties to customize the HT
 </Tabs>
 
 
-```cs
+```csharp
 // Program.cs
 services.AddClientCredentialsTokenManagement(options =>
     {

src/content/docs/accesstokenmanagement/advanced/dpop.md

@@ -44,7 +44,7 @@ Once you have a JWK you wish to use, then it must be configured or made availabl
 
 Here's a sample configuring the key in an application using `AddOpenIdConnectAccessTokenManagement` in the startup code:
 
-```cs
+```csharp
 // Program.cs
 services.AddOpenIdConnectAccessTokenManagement(options =>
 {
@@ -54,7 +54,7 @@ services.AddOpenIdConnectAccessTokenManagement(options =>
 
 Similarly, for an application using `AddClientCredentialsTokenManagement`, it would look like this:
 
-```cs
+```csharp
 // Program.cs
 services.AddClientCredentialsTokenManagement()
    .AddClient("client_name", options =>

src/content/docs/accesstokenmanagement/blazor-server.md

@@ -71,7 +71,7 @@ Once registered and initialized, `Duende.AccessTokenManagement` will keep the st
 
 If you've registered your token store with `AddBlazorServerAccessTokenManagement`, Duende.AccessTokenManagement will register the services necessary to attach tokens to outgoing HTTP requests automatically, using the same API as a non-blazor application. You inject an HTTP client factory and resolve named HTTP clients where ever you need to make HTTP requests, and you register the HTTP client's that use access tokens in the ASP.NET Core service provider with our extension method:
 
-```cs
+```csharp
 // Program.cs
 builder.Services.AddUserAccessTokenHttpClient("demoApiClient", configureClient: client =>
 {

src/content/docs/bff/diagnostics/index.md

@@ -35,7 +35,7 @@ To start emitting OpenTelemetry data in Duende Backend for Frontend (BFF), you n
 
 The following configuration adds the OpenTelemetry configuration to your service setup, and exports data to an [OTLP exporter](https://learn.microsoft.com/en-us/dotnet/core/diagnostics/observability-with-otel):
 
-```cs
+```csharp
 // Program.cs
 var openTelemetry = builder.Services.AddOpenTelemetry();
 

src/content/docs/bff/extensibility/http-forwarder.md

@@ -35,7 +35,7 @@ var client = new HttpMessageInvoker(new SocketsHttpHandler
 
 If you want to customize the HTTP client you can implement the `IForwarderHttpClientFactory` interface, e.g.:
 
-```cs
+```csharp
 public class MyInvokerFactory : IForwarderHttpClientFactory
 {
     public HttpMessageInvoker CreateClient(ForwarderHttpClientContext context)
@@ -59,7 +59,7 @@ public class MyInvokerFactory : IForwarderHttpClientFactory
 
 ...and override our registration:
 
-```cs
+```csharp
 services.AddSingleton<IForwarderHttpClientFactory, MyInvokerFactory>();
 ```
 

src/content/docs/bff/fundamentals/apis/yarp.md

@@ -222,7 +222,7 @@ providing a robust security guarantee.
 
 You can add the anti-forgery protection to all YARP routes by calling the *AsBffApiEndpoint* extension method:
 
-```cs
+```csharp
 app.MapReverseProxy()
     .AsBffApiEndpoint();
 
@@ -253,7 +253,7 @@ the route configuration by adding the *Duende.Bff.Yarp.AntiforgeryCheck* metadat
 
 This is also possible in code:
 
-```cs
+```csharp
 yarpBuilder.LoadFromMemory(
     new[]
     {
@@ -278,7 +278,7 @@ You can combine the token management feature with the anti-forgery check.
 
 To enforce the presence of the anti-forgery headers, you need to add a middleware to the YARP pipeline:
 
-```cs
+```csharp
 // Program.cs
 app.MapReverseProxy(proxyApp =>
 {

src/content/docs/identitymodel-oidcclient/automatic.md

@@ -84,7 +84,7 @@ For a simple example, the following code shows how to use the
 to invoke a browser on the host desktop platform. The `SystemBrowser` is a naive implementation that uses the
 [System.Diagnostics.Process](https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.process) class to start the system default browser.
 
-```cs
+```csharp
 var options = new OidcClientOptions
 {
     Authority = "https://demo.duendesoftware.com",
@@ -99,7 +99,7 @@ var client = new OidcClient(options);
 
 Once the `IBrowser` is configured, the `LoginAsync` method can be invoked to start the authentication flow.
 
-```cs
+```csharp
 var result = await client.LoginAsync();
 ```
 

src/content/docs/identitymodel-oidcclient/logging.md

@@ -11,7 +11,7 @@ redirect_from:
 `OidcClient` logs errors, warnings, and diagnostic information using
 `Microsoft.Extensions.Logging.ILogger`, the standard .NET logging library.
 
-```cs
+```csharp
 using Duende.IdentityModel;
 using Duende.IdentityModel.OidcClient;
 

src/content/docs/identitymodel/endpoints/general-usage.md

@@ -47,7 +47,7 @@ implementation that parses the status codes and response content. The
 following code snippet would parse the raw HTTP response from a token
 endpoint and turn it into a `TokenResponse` object:
 
-```cs
+```csharp
 var tokenResponse = await ProtocolResponse
     .FromHttpResponseAsync<TokenResponse>(httpResponse);
 ```
@@ -65,7 +65,7 @@ object.
 It is your responsibility to set up and manage the lifetime of the
 `HttpClient`, e.g. manually:
 
-```cs
+```csharp
 var client = new HttpClient();
 
 var response = await client.RequestClientCredentialsTokenAsync(
@@ -80,7 +80,7 @@ var response = await client.RequestClientCredentialsTokenAsync(
 You might want to use other techniques to obtain an `HttpClient`, e.g.
 via the HTTP client factory:
 
-```cs
+```csharp
 var client = HttpClientFactory.CreateClient("my_named_token_client");
 
 var response = await client.RequestClientCredentialsTokenAsync(
@@ -112,7 +112,7 @@ Any request type implementing `ProtocolRequest` has the ability to configure
 the client credential style, which specifies how the client will transmit the client ID and secret.
 `ClientCredentialStyle` options include `PostBody` and the default value of `AuthorizationHeader`.
 
-```cs
+```csharp
 var client = HttpClientFactory.CreateClient("my_named_token_client");
 
 var response = await client.RequestClientCredentialsTokenAsync(

src/content/docs/identityserver/apis/aspnetcore/authorization.md

@@ -15,7 +15,7 @@ The access token will include additional claims that can be used for authorizati
 
 In ASP.NET core, the contents of the JWT payload get transformed into claims and packaged up in a `ClaimsPrincipal`. So you can always write custom validation or authorization logic in C#:
 
-```cs
+```csharp
 public IActionResult Get()
 {
     var isAllowed = User.HasClaim("scope", "read");
@@ -28,7 +28,7 @@ For better encapsulation and re-use, consider using the ASP.NET Core [authorizat
 
 With this approach, you would first turn the claim requirement(s) into a named policy:
 
-```cs
+```csharp
 builder.Services.AddAuthorization(options =>
 {
     options.AddPolicy("read_access", policy =>
@@ -38,13 +38,13 @@ builder.Services.AddAuthorization(options =>
 
 ...and then enforce it, e.g. using the routing table:
 
-```cs
+```csharp
 app.MapControllers().RequireAuthorization("read_access");
 ```
 
 ...or imperatively inside the endpoint handler:
 
-```cs
+```csharp
 app.MapGet("/", async (IAuthorizationService authz, ClaimsPrincipal user) =>
 {
     var allowed = await authz.AuthorizeAsync(user, "read_access");
@@ -60,7 +60,7 @@ app.MapGet("/", async (IAuthorizationService authz, ClaimsPrincipal user) =>
 
 ... or declaratively:
 
-```cs
+```csharp
 app.MapGet("/", () =>
 {
     // rest omitted
@@ -73,7 +73,7 @@ Historically, Duende IdentityServer emitted the `scope` claims as an array in th
 
 The newer *JWT Profile for OAuth* [spec](/identityserver/overview/specs.md) mandates that the scope claim is a single space delimited string. You can switch the format by setting the `EmitScopesAsSpaceDelimitedStringInJwt` on the [options](/identityserver/reference/options.md). But this means that the code consuming access tokens might need to be adjusted. The following code can do a conversion to the *multiple claims* format that .NET prefers:
 
-```cs
+```csharp
 namespace IdentityModel.AspNetCore.AccessTokenValidation;
 
 /// <summary>