Configure your identity provider

Create the OIDC client that signs users in to Meko BYOC

Meko BYOC signs users in through your own OpenID Connect (OIDC) identity provider, such as Okta, Keycloak, or Microsoft Entra ID. It has no built-in accounts: without a provider, everyone who reached the address would share one admin account, so the install refuses to run without one.

Create the client

In your identity provider, create an OIDC application (a client) for Meko with these settings:

Setting Value
Flow Authorization code. A public client, which uses PKCE, needs no secret.
Scopes openid, profile, email
Redirect URI <address>/api/v1/auth/oidc/callback
Post-logout redirect URI <address>

<address> is the address Meko is served at, with no trailing slash or path.

  • Production: it is the PUBLIC_URL you chose, for example https://meko.example.com. You know it now, so register both URIs now.
  • Proof of concept: it is the load balancer's host name, which doesn't exist until the install creates it. The install prints both URIs, with the real address, at step 2. Register them then, before anyone signs in.

Register the post-logout URI as well. Without it, your identity provider refuses to sign users out and keeps their session, so the next sign-in doesn't ask for a password.

Microsoft Entra ID refuses a redirect URI that starts with http://. With Entra, set PUBLIC_URL and use the production setup, even for a trial.

Collect the values

Install variable Value
OIDC_ISSUER_URL The issuer. It must serve /.well-known/openid-configuration, and the cluster must be able to reach it. For Keycloak it looks like https://<host>/realms/<realm>. For Okta, https://<org>.okta.com/oauth2/default.
OIDC_CLIENT_ID The client's ID
OIDC_CLIENT_SECRET The client's secret. Leave it empty for a public client.

Create a user for the reconcile agent

Create one more user in your identity provider, kept for the reconcile agent alone. After the install, you sign in to Meko as this user once, to create the agent's API key. Everything the agent creates, such as the datapacks Meko declares for your environment, then belongs to this account and not to a person. People see those datapacks when you share them from it.

Next

Prepare the cluster and network.