Sign-in and providers
Weik.io 2026.2People sign in to the admin UI through an OpenID Connect provider such as Microsoft Entra ID, or with a local account. 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. weikio login gets a key through the approval page of your Weik.io installation in the browser.
Weik.io issues every token and signs it with ES256 keys, which it stores encrypted and rotates every 90 days.
Add Microsoft Entra ID#
-
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 setaccepts the value as 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. Then only people from those tenants can sign in.
Weik.io signs people in with OpenID Connect and never calls Microsoft Graph. 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. A person who signs in through the provider with a mapped app role or group gets the mapping’s grant.
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 you set another claim with --claim-path.
$ 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. To remove one, run weikio delete mapping <id>.
When you delete a mapping, its grants end in people’s sessions within 15 minutes if the provider issues refresh tokens, and otherwise at their next sign-in.
A person signed in through a provider has the grants you gave them and the mapped grants. Their keys from weikio login and the All my access keys they made while signed in through the provider have the mapped grants too, for 30 days after their last sign-in there. An Only these key never has mapped grants, only what you gave its owner with weikio member add.
To change the 30 days, run weikio provider set entra --roles-count-for 7d with your provider’s name and the number of days you need. With 0, no key gets the provider’s roles. weikio describe provider shows the setting. weikio whoami shows whether your key still has the provider’s roles, as Check what you can do describes.
To see what a provider last sent for a person, run weikio describe user with their e-mail. Its SIGN-IN CLAIMS table lists the values the provider sent for the claim your mappings use, when the person last signed in. Next to each value is the ID of the mapping it matched, or - when none matched. In the admin UI, open Sign-in claims from your user menu, or from a person’s row on the Users page.
none in the table means the provider sent the claim with no values, so no mapping matched. Add the claim to the ID token at the provider, or set --claim-path to a claim the provider sends. You can see a person’s claims for 12 hours longer than the days you set with --roles-count-for. By default, that’s 30 days and 12 hours.
Limit local accounts#
Once federated sign-in works, let local accounts sign in only for emergencies:
$ weikio settings set --local-accounts breakGlassOnlyFrom then on, only a break-glass account can sign in with a password, and only while a break-glass window is open. Once you’ve added a provider, the Providers page shows this setting as a suggestion while 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. 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, encrypted with the master key. Five wrong passwords for one account from one address within 15 minutes lock that address out of the account for 15 minutes. Sign-ins to the account from other addresses still work, but five wrong two-factor codes lock the account for every address.
A known issue in 2026.2.4: someone who keeps switching addresses avoids the password lock. An account-wide limit is planned for 2026.2.5.
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.
Changing your password ends your other sessions.