Skip to main content
Most Cake Platform applications use single sign-on, so your users sign in with your organization’s identity provider. A few applications also have a built-in admin account. Cake generates the password for each of those accounts inside the cluster and stores it in a Kubernetes secret.

Sign in with single sign-on

The platform uses Dex as its identity broker at https://<base-hostname>/dex. Cake connects Dex to your identity provider during installation. Dex supports:
  • Google Workspace, optionally restricted to specific domains and groups
  • Microsoft Entra ID
  • Any OpenID Connect (OIDC) provider
  • Local accounts with static passwords
To sign in, open an application URL from the components list and choose your identity provider on the Dex login page. To change which identity provider or domains can sign in, update app_config.dex in your vars file.

Platform admins

Cake assigns the cake-admin role to the users you name as platform admins. Users with the cake-admin role get:
  • The admin role in Argo CD
  • The Admin role in Grafana. Other users sign in to Grafana as Viewer.
  • The cake-admin Kubernetes ClusterRole for their identity in the cluster
Argo CD and Grafana have no local admin login. You reach them only through single sign-on.

Retrieve generated credentials

The following applications have an admin account that Cake creates with a generated password. You read each password from a Kubernetes secret, so you need cluster access first. See Access the Kubernetes cluster. The namespaces above are the defaults. A project instance of an application runs in its own namespace. To find the right namespace, list the secrets across all namespaces:

LiteLLM master key

The LiteLLM master key starts with sk-. Use it to call the LiteLLM admin API, create virtual keys for your users, and sign in to the LiteLLM admin UI.

Langflow superuser

Langflow signs users in automatically. Use the superuser account for administrative tasks in Langflow.

Trino password

Use the Trino username and password to connect JDBC clients and other SQL tools to trino.<base-hostname>.
These credentials grant admin access. Store them in your organization’s secrets manager and share them only with the people who need them.