Token Server

The token server provides the data plane for ServiceAuthCentral in the form of the token endpoint used to vend the JWT access tokens.

Overview

The token server provides two major functions. First is providing the JWKS endpoint to resource servers. The public keys are retrieved from the specific implementation of the sign module. And the primary function is providing the OAuth 2.0 endpoint for clients to request access tokens which are returned in the form of JWTs.

flowchart LR
    subgraph SAC[ServiceAuthCentral]
        TokenServer[Token Server]

        subgraph Sign
            PrivateKey[Private Key]
            PublicKey[Public Key]
        end

        subgraph DataModel[Data Model]
            authorizations[(authorizations)]
            clients[(clients)]
        end

        TokenServer -- Get Authorization--> authorizations
        TokenServer -- Get Client--> clients

        TokenServer -- Get Public Key--> PublicKey
        TokenServer -- Sign JWT --> PrivateKey
    end

    ResourceServer[Resource Server]
    ResourceServer -- GET JWKS --> TokenServer

    Client -- Request Token --> TokenServer

    Client -. API Call.-> ResourceServer

Build Token Server Docker Image

Both the manage and token service are compiled from the same repository git repository and Dockerfile. The command to build the token server requires the correct build-arg to be passed in to generate the docker container for the token server components.

docker build -f Dockerfile --build-arg MAVEN_PROFILE=server-token -t serviceauthcentral/server-token .

Run Token Server Using Docker

The Docker image for the token server is configured using environment variables.