Private Key JWTs

The OpenID Connect specification recommends a client authentication method based on asymmetric keys. With this approach, instead of transmitting the shared secret over the network, the client creates a JWT and signs it with its private key. Your IdentityServer only needs to store the corresponding key to be able to validate the signature.

The technique is described here and is based on the OAuth JWT assertion specification (RFC 7523).

Setting up a private key JWT secret

The default default private key JWT secret validator expects either a base64 encoded X.509 certificate or a JSON Web Key formatted RSA, EC or symmetric key on the secret definition:

var client = new Client
    ClientId = "client.jwt",

    ClientSecrets =
        new Secret
            // base64 encoded X.509 certificate
            Type = IdentityServerConstants.SecretTypes.X509CertificateBase64,

            Value = "MIID...xBXQ="
        new Secret
            // JWK formatted RSA key
            Type = IdentityServerConstants.SecretTypes.JsonWebKey,

            Value = "{'e':'AQAB','kid':'Zz...GEA','kty':'RSA','n':'wWw...etgKw'}"

    AllowedGrantTypes = GrantTypes.ClientCredentials,
    AllowedScopes = { "api1", "api2" }

You can share the same key for client authentication and signed authorize requests.

Authentication using a private key JWT

On the client side the, the caller must first generate the JWT, and then send it on the assertion body field:

POST /connect/token

Content-type: application/x-www-form-urlencoded



.NET client library

You can use the Microsoft JWT library to create JSON Web Tokens.

private static string CreateClientToken(SigningCredentials credential, string clientId, string audience)
    var now = DateTime.UtcNow;

    var token = new JwtSecurityToken(
        new List<Claim>()
            new Claim(JwtClaimTypes.JwtId, Guid.NewGuid().ToString()),
            new Claim(JwtClaimTypes.Subject, clientId),
            new Claim(JwtClaimTypes.IssuedAt, now.ToEpochTime().ToString(), ClaimValueTypes.Integer64)

    var tokenHandler = new JwtSecurityTokenHandler();
    return tokenHandler.WriteToken(token);

..and the IdentityModel client library to programmatically interact with the protocol endpoint from .NET code.

using IdentityModel.Client;

static async Task<TokenResponse> RequestTokenAsync(SigningCredentials credential)
    var client = new HttpClient();

    var disco = await client.GetDiscoveryDocumentAsync("");
    if (disco.IsError) throw new Exception(disco.Error);

    var clientToken = CreateClientToken(credential, "private.key.jwt", disco.TokenEndpoint);

    var response = await client.RequestClientCredentialsTokenAsync(new ClientCredentialsTokenRequest
        Address = disco.TokenEndpoint,
        Scope = "api1.scope1",

        ClientAssertion =
            Type = OidcConstants.ClientAssertionTypes.JwtBearer,
            Value = clientToken

    if (response.IsError) throw new Exception(response.Error);
    return response;

See here for a sample for using JWT-based authentication.

Using ASP.NET Core

The OpenID Connect authentication handler in ASP.NET Core allows for replacing a static client secret with a dynamically created client assertion.

This is accomplished by handling the various events on the handler. We recommend to encapsulate the event handler in a separate type. This makes it easier to consume services from DI:

public void ConfigureServices(IServiceCollection services)
    // some details omitted

    services.AddAuthentication(options =>
        .AddOpenIdConnect("oidc", options =>
            options.Authority = Constants.Authority;

            // no static client secret        
            options.ClientId = "mvc.jar.jwt";

            // specifies type that handles events
            options.EventsType = typeof(OidcEvents);        

In your event handler you can inject code before the handler redeems the code:

public class OidcEvents : OpenIdConnectEvents
    private readonly AssertionService _assertionService;

    public OidcEvents(AssertionService assertionService)
        _assertionService = assertionService;
    public override Task AuthorizationCodeReceived(AuthorizationCodeReceivedContext context)
        context.TokenEndpointRequest.ClientAssertionType = OidcConstants.ClientAssertionTypes.JwtBearer;
        context.TokenEndpointRequest.ClientAssertion = _assertionService.CreateClientToken();

        return Task.CompletedTask;

The assertion service would be a helper to create the JWT as shown above in the CreateClientToken method. See here for a sample for using JWT-based authentication (and signed authorize requests) in ASP.NET Core.