KubeMQ's Authentication feature allows controlling the access of clients to KubeMQ gRPC and Rest interfaces.

How Authentication Works

Clients Authentication connectivity When a client connects to KubeMQ, and before it can perform operations, it must authenticate, that is, present and prove its identity.

The way KubeMQ authenticate the client identity is the support JWT (Jason Web Token) authentication.

Every request must present a valid JWT token (generated by any JWT provider) and verified by a public key that configured in KubeMQ.

Authentication Configuration

KubeMQ's JWT support requires two parameters:

  1. Public Key

  2. Public Key Signature type

Each signing method expects a different object type for its signing keys. Here are the supported ones:

  • The HMAC signing method - (HS256,HS384,HS512).

  • The RSA signing method - (RS256,RS384,RS512).

  • The ECDSA signing method - (ES256,ES384,ES512).

Loading Configuration

pageSet Authentication

The Authentication feature is available only on KubeMQ Enterprise Edition.

Register for free 30 days license here.

Last updated