Sign-in and providers
Weik.io 2026.2People sign in to the admin UI through Microsoft Entra ID, another OpenID Connect provider or a local account, and claim mappings turn a provider's app roles or groups into grants.
On this page
People sign in to the admin UI through the identity providers you add, or with a local account’s e-mail and password. Each provider you add gets its own button on the sign-in page.
The weikio CLI and your pipelines sign in with API keys, and weikio login gets a key through the approval page of your Weik.io installation in the browser.
The backend issues and signs every token itself, with ES256 keys that it keeps sealed and rotates every 90 days.
Add Microsoft Entra ID#
To add Microsoft Entra ID, follow these steps:
-
Register an application for Weik.io in your Entra tenant.
-
Create a project that you won’t delete, such as
platform, and set the application’s client secret there.weikio secret setasks for the value with hidden input:Terminal$ weikio project create platform $ weikio secret set platform/entra-client-secret -
Add the provider.
--display-namesets the name on the sign-in button, so this provider’s button saysContinue with Microsoft:Terminal$ weikio provider set entra --kind entra --tenant <tenant-id> --client-id <id> --client-secret-ref platform.entra-client-secret --display-name Microsoft -
At the provider, register the redirect URI that the command prints, which is
https://acme.example/api/v1/auth/callback/entrafor an installation atacme.example.
A tenant ID limits sign-in to that tenant. To admit several tenants, give the tenant as organizations or common and list the tenants to admit with --allowed-tenant. Weik.io then accepts tokens of those tenants only.
Sign-in uses OpenID Connect, and Weik.io calls no Microsoft Graph address. During a sign-in it reaches only the provider’s discovery document and its key and token addresses.
Add an OpenID Connect provider#
Add any other OpenID Connect provider, such as Keycloak or a sovereign cloud’s sign-in, as a provider of kind oidc with its issuer address. Its client secret goes in the same project:
$ weikio secret set platform/keycloak-client-secret
$ weikio provider set keycloak --kind oidc --authority https://sso.acme.example/realms/acme --client-id weikio --client-secret-ref platform.keycloak-client-secret --display-name "Acme SSO"weikio get providers lists the providers. weikio describe provider entra shows one provider with its redirect URI and whether Weik.io finds its client secret. In the admin UI, Settings › Access › Providers shows the same.
Claim mappings#
Use a claim mapping to give grants from your provider’s app roles or groups. The mapping turns a value the provider puts in its token into a grant at every sign-in through that provider.
An Entra provider’s mappings use the roles claim, which has the app roles, or the groups claim when a token has no roles. Any other provider uses the groups claim unless --claim-path gives another claim.
$ weikio mapping add entra groups <group-id> --grant finance/deployer@productionWithout --integrations and --apis, a mapping covers the whole project. With either, it covers only the integrations and APIs it lists. --platform-admin makes the members of a group platform administrators.
weikio get mappings lists the mappings with their IDs, and weikio delete mapping <id> removes one.
When you delete a mapping, the grants it gave end within 15 minutes in every session whose provider gave a refresh token, and in the other sessions at the next sign-in.
A session signed in through a provider has both the person’s local grant and the mapped grants. API keys never get mapped grants, so a key has only what was granted to its owner directly with weikio member add.
Limit local accounts#
Once federated sign-in works, let local accounts sign in only for emergencies:
$ weikio settings set --local-accounts breakGlassOnlyFrom then on Weik.io accepts a password sign-in only from a break-glass account, and only while a break-glass window is open. Once you’ve added a provider, the Providers page suggests this setting for as long as local accounts are open to everyone.
Local sign-in#
While local accounts are on, a platform administrator creates them with weikio user create, which prints a one-time set-password link valid for 72 hours, and weikio user reset-password issues a new link.
Weik.io accepts a password of 12 to 1,024 characters and stores it as a PBKDF2-SHA256 hash with 600,000 iterations, sealed with the master key. Five wrong sign-in attempts for one account within 15 minutes lock it for 15 minutes.
Platform administrators and break-glass accounts give a code from an authenticator app at every local sign-in, as Two-factor sign-in describes. A federated sign-in uses the provider’s second factor.
The browser session#
Weik.io stores each browser session, so whichever backend answers the next request knows it. Changing your password ends your other sessions.