JWT Auth

Diagram

sequenceDiagram
    participant Client as Client Application
    participant Issuer as JWT Issuer
    participant Infis as Hanzo KMS

    Client->>Issuer: Step 1: Request JWT token
    Issuer-->>Client: Return signed JWT with claims

    Note over Client,Infis: Step 2: Login Operation
    Client->>Infis: Send signed JWT to /api/v1/auth/jwt-auth/login

    Note over Infis: Step 3: JWT Validation
    Infis->>Infis: Validate JWT signature using configured public keys or JWKS
    Infis->>Infis: Verify required claims (aud, sub, iss)

    Note over Infis: Step 4: Token Generation
    Infis->>Client: Return short-lived access token

    Note over Client,Infis: Step 5: Access Hanzo KMS API with Token
    Client->>Infis: Make authenticated requests using the short-lived access token

Concept

Feedback
The client requests a JWT from their JWT issuer.
Feedback
The fetched JWT is sent to Hanzo KMS at the /api/v1/auth/jwt-auth/login endpoint.
Feedback
Hanzo KMS validates the JWT signature using either:
• Pre-configured public keys (Static configuration)
• Public keys fetched from a JWKS endpoint (JWKS configuration)
Feedback
Hanzo KMS verifies that the configured claims match in the token. This includes standard claims like subject, audience, and issuer, as well as any additional custom claims specified in the configuration.
Feedback
If all is well, Hanzo KMS returns a short-lived access token that the client can use to make authenticated requests to the Hanzo KMS API.

For JWKS configuration, Hanzo KMS needs network-level access to the configured JWKS endpoint.

Guide

To create an identity, head to your Organization Settings > Access Control > Identities and press Create identity.

When creating an identity, you specify an organization level role for it to assume; you can configure roles in Organization Settings > Access Control > Organization Roles.

Now input a few details for your new identity. Here's some guidance for each field:

• Name (required): A friendly name for the identity.
• Role (required): A role from the Organization Roles tab for the identity to assume. The organization role assigned will determine what organization level resources this identity can have access to.

Once you've created an identity, you'll be redirected to a page where you can manage the identity.

Since the identity has been configured with Universal Auth by default, you should re-configure it to use JWT Auth instead. To do this, press to edit the Authentication section, remove the existing Universal Auth configuration, and add a new JWT Auth configuration onto the identity.

Here's some more guidance for each field:

Static configuration:

• Public Keys: One or more PEM-encoded public keys (RSA or ECDSA) used to verify JWT signatures. Each key must include the proper BEGIN/END markers.

JWKS configuration:

• JWKS URL: The endpoint URL that serves your JSON Web Key Sets (JWKS). This endpoint must provide the public keys used for JWT signature verification.
• JWKS CA Certificate: Optional PEM-encoded CA certificate used for validating the TLS connection to the JWKS endpoint.

Common fields for both configurations:

• Issuer: The unique identifier of the JWT provider. This value is used to verify the iss (issuer) claim in the JWT.
• Audiences: A list of intended recipients. This value is checked against the aud (audience) claim in the token.
• Subject: The expected principal that is the subject of the JWT. This value is checked against the sub (subject) claim in the token.
• Claims: Additional claims that must be present in the JWT for it to be valid. You can specify required claim names and their expected values.
• Access Token TTL (default is 2592000 equivalent to 30 days): The lifetime for an access token in seconds. This value will be referenced at renewal time.
• Access Token Max TTL (default is 2592000 equivalent to 30 days): The maximum lifetime for an access token in seconds. This value will be referenced at renewal time.
• Access Token Max Number of Uses (default is 0): The maximum number of times that an access token can be used; a value of 0 implies infinite number of uses.
• Access Token Trusted IPs: The IPs or CIDR ranges that access tokens can be used from. By default, each token is given the 0.0.0.0/0, allowing usage from any network address.

To enable the identity to access project-level resources such as secrets within a specific project, you should add it to that project.

To do this, head over to the project you want to add the identity to and go to Project Settings > Access Control > Machine Identities and press Add identity.

Next, select the identity you want to add to the project and the project level role you want to allow it to assume. The project role assigned will determine what project level resources this identity can have access to.

To access the Hanzo KMS API as the identity, you will need to obtain a JWT from your JWT issuer that meets the validation requirements configured in step 2.

Once you have obtained a valid JWT, you can use it to authenticate with Hanzo KMS at the /api/v1/auth/jwt-auth/login endpoint.

We provide a code example below of how you might use the JWT to authenticate with Hanzo KMS to gain access to the Hanzo KMS API.

The shown example uses Node.js but you can use any other language to authenticate with Hanzo KMS using your JWT.

try {
    // Obtain JWT from your issuer
    const jwt = "<your-jwt-token>";

    const kmsUrl = "https://app.kms.hanzo.ai"; // or your self-hosted Hanzo KMS URL
    const identityId = "<your-identity-id>";

    const { data } = await axios.post(
        `{kmsUrl}/api/v1/auth/jwt-auth/login`,
        {
            identityId,
            jwt,
        }
    );

    console.log("result data: ", data); // access token here
} catch(err) {
    console.error(err);
}

We recommend using one of Hanzo KMS's clients like SDKs or the KMS Agent to authenticate with Hanzo KMS using JWT Auth as they handle the authentication process for you.

Each identity access token has a time-to-live (TTL) which you can infer from the response of the login operation; the default TTL is 2592000 seconds (30 days) which can be adjusted in the configuration.

If an identity access token exceeds its max TTL or maximum number of uses, it can no longer authenticate with the Hanzo KMS API. In this case, a new access token should be obtained by performing another login operation with a valid JWT.