Streaming

Redpanda Console Security

This section pertains to Redpanda Console in a self-hosted deployment.
  • Authentication

    Redpanda Console supports authentication using OAuth 2.0 or OIDC for external identity providers.

  • Authorization

    Redpanda Console uses role-based access control (RBAC) to restrict system access to authorized users.

  • Azure AD SSO Authentication in Redpanda Console

    Integrate Redpanda Console with Azure AD to allow your users to use their Azure AD identities to sign-in to Console.

  • GitHub SSO Setup

    Integrate Redpanda Console with GitHub to allow your users to use their GitHub identities to sign-in to Console.

  • Generic OIDC

    Integrate your Redpanda Console authentication with any identity provider that supports an OIDC-compatible protocol.

  • Google SSO Setup

    Integrate Redpanda Console with Google to allow your users to use their Google identities to sign in to Console.

  • Keycloak SSO Authentication in Redpanda Console

    Integrate Redpanda Console with Keycloak to allow your users to use their Keycloak identities to sign-in to Console.

  • Okta SSO Setup

    Integrate Redpanda Console with Okta to allow your users to use their Okta identities to sign in to Redpanda Console.

  • Plain Login Setup

    Configure Redpanda Console with a plain login provider to allow your users to authenticate with a predefined username and password.

  • TLS Termination

    To secure Redpanda Console using TLS, you can let Redpanda Console handle TLS termination or you can offload it to an upstream component, such as a reverse proxy or a Cloud HTTPS LoadBalancer.