Dex

Authenticate on-premises AxoConsole users with an existing identity system through Dex, and switch over from the built-in provider.

Dex is an open-source identity federation layer. When you configure AxoConsole to use Dex, Dex handles authentication with your existing identity system and passes user identity back to AxoConsole.

The following connectors are supported:

LDAP — connect to an LDAP or Active Directory server
GitHub — authenticate with GitHub OAuth
Google — authenticate with Google accounts or Google Groups

Switch from the built-in provider to Dex

Make sure that the idp.<your-host.your-domain> subdomain resolves to the AxoConsole IP address from your desktop and from every AxoRouter and Axoflow agent host, for example, by adding it to the DNS or to the /etc/hosts files. Dex is served on this subdomain, unlike the built-in provider, and the prepare-axorouter-host.sh script generated by the installer doesn’t add it.

Configure Dex as the OIDC provider in the /var/lib/rancher/k3s/server/manifests/axoflow-config.yaml file. For example:

chalco:
  oidc:
    enabled: true
    provider: "dex"

axoidp:
  enabled: false

dex:
  enabled: true

After saving the file, k3s automatically applies the changes. Users will be redirected to the Dex login page on next login.

GitHub

Log in to an on-premises AxoConsole with the GitHub accounts of your organization, using a GitHub OAuth application and Dex.

Google

LDAP