Skip to content

Documentation

Users, roles and sign-in

This guide explains how people and scripts sign in to LEA Platform, what each role may do, and how to set up single sign-on, local accounts and tokens. It ends with what to do when nobody can sign in.

Before you start

  • You need the Administrator role (or a role with the Users and sign-in permission) for single sign-on, local users and access. People with the Viewer role do not see Settings or Audit in the left menu.
  • For single sign-on you need someone who can register an application in your identity provider (for example Microsoft Entra ID, Okta or Keycloak).
  • For recovery tasks you need a shell on the LEA server, in the release directory (usually /opt/lea/lea_release).

How signing in works

LEA Platform has two ways to sign in to the console:

WayWho uses itWhat the sign-in page shows
Single sign-on (SSO)Everybody, once an identity provider is enabledOne button per provider: Sign in with <provider name>
Local accountEverybody until SSO is enabled; afterwards only in an emergency (break-glass)Username, Password and Sign in
  • An identity provider is your company sign-in service (Microsoft Entra ID, Okta, Keycloak, and so on). LEA Platform talks to it with OpenID Connect. SAML is not supported.
  • While no identity provider is enabled, local users sign in with a password.
  • As soon as one provider is enabled, password sign-in to the console stops. The link Sign in with a local account only appears while a break-glass window is open. See Open a break-glass window.
  • A local sign-in during SSO is written to the audit log and administrators get a notification.

The sign-in page explains why you landed there:

MessageWhat it means
You are signed out.You clicked Log out.
Your session ended. Sign in again.You were idle too long, the maximum session time passed, or an administrator ended your session.
You do not have access to LEA Platform yet. An administrator has been asked to review your request.Your identity provider knows you, but no role mapping gives you a LEA role. See Approve an access request.
This sign-in requires multi-factor authentication.The provider has Require multi-factor authentication (amr/acr) on and your sign-in did not use MFA.
Your identity provider sent too many groups.Microsoft Entra ID only: use app roles instead of groups.

The full list of error codes is in the sign-in reference.

Note: Your account menu is the Welcome, <your name> button at the top right. It shows how you signed in ("Signed in with …", "Local account" or "Local account (break-glass)") and has Account settings, SSO account (when your administrator set an account page) and Log out.

Roles and what they can do

LEA Platform has six built-in roles. Role mappings, grants and local users can also limit a role to some host groups (a scope).

RoleCan do
ViewerView the dashboard, compliance, execution results, rules, groups, hosts, functions (not their code), reports, agent logs and the AI assistant (questions only). Manage their own notifications and command-line sign-ins. Secret rule parameter values are hidden.
AuditorEverything Viewer can do, plus the audit log and compliance reports with evidence.
OperatorEverything Viewer can do, plus handle notifications, run remedies, manage hosts (activate, deactivate, re-enroll, delete), run ad-hoc commands, edit groups, assign rules to groups and remove results.
EngineerEverything Operator can do, plus rules (including secret values), rule rollouts, rule packs and functions.
Administrator (admin)Every permission: all of the above plus settings, users, sign-in, tokens, webhooks, the cluster and the license. The AI assistant can propose changes for administrators.
IntegrationFor programs: see the fleet, rules and compliance reports.

Read (shown as read or "Viewer (read)") is the older name of Viewer and gives the same access. The full list of permissions, scopes and how to check what one person can do is in Access: roles and scopes.

Where the role comes from:

  • SSO users: from the role mappings of their identity provider, recomputed at every sign-in and every re-check, plus any grants. See Map identity provider groups to roles.
  • Local users and API accounts: from the Role and Scope fields of the account. See Give a local user a role and scope.
  • Tokens: the token follows its owner's current role. A token never gives more than its owner has.

Turn on single sign-on

Do this once per identity provider. You can enable several providers; each gets its own button on the sign-in page.

  1. Open Settings → Single sign-on.

  2. On the Identity providers tab, click Add provider.

  3. In Type, pick your identity provider. The type fills in the scopes, the role claims and default role mappings.

    TypeFields you fill in
    Microsoft Entra IDDirectory (tenant) ID (single tenant only)
    OktaOkta domain, Authorization server (default)
    Auth0Auth0 domain
    Google WorkspaceWorkspace domain (only accounts of this domain can sign in)
    PingOneRegion, Environment ID
    PingFederateIssuer URL
    OneLoginSubdomain
    JumpCloudnothing extra
    Keycloak / Red Hat build of KeycloakBase URL, Realm
    AD FS (2016+)AD FS host
    Amazon CognitoRegion, User pool ID
    authentikBase URL, Application slug
    ZITADELInstance URL
    GitLab (self-managed or gitlab.com)GitLab URL
    Generic OpenID ConnectIssuer URL
  4. Fill in Button label (shown as "Sign in with …"), Slug (a short name used in the URLs, a-z, 0-9 and -) and Client ID (the application ID your identity provider gave LEA Platform).

  5. Leave Scopes and everything under Advanced as they are unless your identity team asks for a change.

  6. Click Create provider.

    You should see: "Provider created. Register the URLs below in your identity provider, add a credential, test and enable it." The provider is created disabled.

  7. Under Register in your identity provider, copy each URL with its copy button into your identity provider: Redirect URI, Post-logout redirect URI, and the Front-channel logout URL (Microsoft Entra ID) or Back-channel logout URL (most others). The redirect URI must match exactly. The box above the URLs has short setup steps for Entra ID, Okta, Keycloak and Google.

  8. Under Client credential, choose one:

    • Generate certificate (recommended). LEA Platform keeps the private key. Download Certificate (.cer) or JWKS (.json) and upload it to your identity provider.
    • Or paste the identity provider's secret into Client secret, set Secret expires, and click Use client secret.
    • Keycloak and Generic only: Use public client if your provider has no client secret.
  9. Review Role mappings (next section). Without a mapping nobody gets in.

  10. Under Connection test, click Run test.

    You should see a list of checks, each marked OK, WARN or ERROR. Fix every ERROR before you continue.

  11. Turn on the switch at the top right of the dialog (it changes from Disabled to Enabled). Enabling checks the provider and its credential again.

  12. Click Close. Open a private browser window and sign in with the new button to confirm it works.

Important: Before you enable the first provider, make sure at least one person's group maps to Admin. Keep one local admin account, disabled, for emergencies. See Open a break-glass window.

Tip: If the LEA server reaches the identity provider through a different address than your browsers do, set Backend URL under Advanced. If your identity provider uses certificates from your own certificate authority, paste the CA into CA certificates (PEM). Both are common on sites without internet.

Step-by-step instructions for Microsoft Entra ID (app roles, assignment, MFA) and SCIM provisioning are in the sign-in reference.

Read the identity provider list

The Identity providers tab lists every provider with a status: ENABLED, DISABLED, NEEDS CREDENTIAL, ERROR or CREDENTIAL EXPIRING. Rotate an expiring certificate with Rotate certificate in the provider dialog, then upload the new certificate to the identity provider.

Column or statusWhat it means
TypeThe kind of identity provider, for example Microsoft Entra ID or Okta. It sets the default scopes, role claims and role mappings.
Client authenticationHow LEA Platform proves its own identity to the provider when it collects a sign-in: a certificate, a client secret, or none (public client).
Credential expiresWhen the certificate or client secret that LEA Platform uses with this provider stops working. Renew it before then.
IdentitiesHow many people and applications LEA Platform has seen through this provider. They are listed on the Identities tab.
SessionsHow many console sessions signed in through this provider are open now.
NEEDS CREDENTIALThe provider has no certificate or client secret yet, so it cannot be enabled. Add one under Client credential.
CREDENTIAL EXPIRINGThe certificate or client secret expires within 30 days; after that nobody can sign in with this provider. Rotate or renew it now.

Provisioning (SCIM 2.0)

SCIM lets your identity provider create, update and deactivate LEA identities and groups by itself. Under Provisioning (SCIM 2.0) in the provider dialog, copy the SCIM base URL and create a token for your identity provider. The token is shown only once. Steps for Microsoft Entra ID are in the sign-in reference.

ButtonWhat it does
Create token / Rotate tokenMakes a new token your identity provider uses to send users and groups. Any older token stops working at once.
Revoke tokenDeletes the token, so the identity provider can no longer send users and groups.

Map identity provider groups to roles

Role mappings are the allow-list. A mapping says: "when this claim has this value, give this LEA role, on everything or on these host groups".

  1. Open Settings → Single sign-on and click the provider in the list.
  2. Scroll to Role mappings and click Add mapping.
  3. In Claim, pick or type the claim name. Common ones: groups, roles, email, scim_groups (groups sent by SCIM provisioning).
  4. In Value, type the exact value. For Entra ID this is an app role value (for example LEA.Admin) or a group object ID, not the group's display name.
  5. In Role, pick one of the built-in roles, for example Operator.
  6. Optionally, in Scope, pick the host groups the role is limited to. Leave it empty for everything.
  7. Click Save.

To change a mapping, click its row. All mappings of all providers are also listed on Settings → Access → Bindings; see Give a team access to some host groups.

Rules to remember:

  • Several matches add up: the person gets the permissions of every matching mapping. A role given for everything wins over the same role on some groups.
  • No match means no access. The person sees "You do not have access…" and an access request is recorded.
  • The identity provider wins. If someone leaves the group, they lose the role at the next sign-in or re-check (default every 10 minutes).
ColumnWhat it shows
ClaimThe name of a field in the sign-in token from the identity provider, such as groups or roles, that this mapping looks at.
ValueThe exact text the claim must contain for the mapping to apply, for example an app role or a group ID.
LEA roleThe built-in role a person gets in LEA Platform when the claim has that value, for example Operator or Administrator.
ScopeThe host groups the role is limited to, or Everything when the mapping applies to the whole platform.

Default mappings per type, for example:

TypeClaimValueRole
Microsoft Entra IDrolesLEA.AdminAdministrator
Microsoft Entra IDrolesLEA.ReaderViewer (read)
OktagroupsLEA AdminsAdministrator
Keycloakresource_access.<client id>.roleslea_adminAdministrator

Approve an access request

When someone signs in but matches no role mapping, LEA Platform records an access request and notifies administrators.

  1. Open Settings → Single sign-on and click the Access requests tab. The number in brackets is the number of pending requests.
  2. Click a row to see the claims the identity provider sent. This tells you which group or role to map.
  3. Choose one:
    • Approve: pick a Role, optionally a Scope (host groups), Expires after (days) and a Reason, then click Approve. This grants the role to this one person only.
    • Block: refuses this identity and stops future requests from it.
    • Dismiss: removes the request without a decision.
Column or buttonWhat it means
KindWhether the identity is a person (USER) or a program that calls the API with its own identity provider token (APP).
AttemptsHow many times this identity tried to sign in or call the API without a role since the request was first recorded.
ApproveGives this one identity a LEA role, optionally for a limited number of days, without a role mapping.

Tip: Approving one person at a time does not scale. Prefer adding a role mapping for their group, so everyone in the group gets in.

To stop recording access requests, turn off Record access requests from identities without a role on the Policy tab.

Manage identities and sessions

The Identities tab lists every person and application seen through your identity providers, with their role, how they got it, last sign-in and number of sessions and tokens.

ButtonWhat it does
GrantGives this identity a role on top of its mappings, optionally on some host groups and for a number of days. A person can have several grants.
Disable / EnableDisable ends the person's sessions and revokes their tokens. They cannot sign in until enabled again.
Sign-out icon ("End sessions and revoke tokens")Signs the person out everywhere and stops all their personal access tokens, without disabling them.

Click a row to list the person's grants with their role, scope, expiry and reason. The bin icon (Remove grant) takes one back. To see everything a person can do, open Settings → Access → Effective access.

ColumnWhat it shows
KindUSER for a person, APP for a program that calls the API with its own identity provider token.
RoleThe highest built-in role the identity had at its last sign-in, from its mappings and grants; "has grants" when it also holds grants.
SourceHow the identity reached LEA Platform: LOGIN (signed in to the console), API (called the API) or SCIM (sent by the identity provider's provisioning).
Sessions / tokensConsole sessions of this identity open now, and its tokens that are not revoked (personal access tokens and command-line sign-ins).

The Sessions tab lists active console sessions (method, role, MFA, address, start and last activity). Click End to sign that browser out within seconds. Your own session is marked "(this session)".

ColumnWhat it shows
MethodThe identity provider this session signed in through, or LOCAL for a local account with a password.
LOCALThe session signed in with a local account and password, not through single sign-on.
MFAYes when the identity provider reported that this sign-in used multi-factor authentication, such as a code or a security key.

Set the sign-in policy

The Policy tab of Settings → Single sign-on holds the rules for sessions and tokens. Change a value, then click Save.

FieldWhat it controlsDefault
Idle timeout (minutes)Sign out after this much inactivity60
Maximum session (hours)Sign in again after this long, active or not12
Identity provider re-check (minutes)How often an active session is checked with the identity provider10
Provider outage grace (minutes)How long sessions survive when the identity provider cannot be reached30
Token default lifetime (days)Expiry of a personal access token or CLI sign-in when none is chosen90
Token maximum lifetime (days)Upper limit for personal access tokens365
Token owner inactivity (days)Tokens of SSO users stop working when the owner has not signed in to the console for this long90
Token claim freshness (hours)SSO token owners must sign in again when their stored identity provider claims are older than this; 1–168 hours allowed24
Break-glass maximum (minutes)Longest break-glass window the server can open480 (8 hours)
Public URLThe address used in redirect and logout URLs when LEA Platform is behind a proxy with another host nameempty

Switches under Behaviour:

  • Signing out of LEA also signs out of the identity provider (on by default).
  • Record access requests from identities without a role.
  • Allow the legacy password API (/lea/authenticate_api) for local users while single sign-on is on. Leave this off. Old scripts should use an API account or a personal access token instead.

Limit token claim age

Token claim freshness limits how old an SSO token owner's stored identity provider roles and groups may be.

  1. Open Settings → Single sign-on and select Policy.
  2. Under Sessions and tokens, set Token claim freshness (hours) from 1 to 168 hours. The default is 24 hours.
  3. Click Save. Confirm it is you if your security policy requires it.

You should see: "Sign-in policy saved."

SSO personal access tokens and CLI sign-ins pause after this limit until fresh claims arrive. Using a token does not renew it. Sign in again to resume a token if you still have access. This limit is separate from Token owner inactivity (days) in the same Policy tab; both apply. Local accounts and application identities keep their existing behavior. See Create a personal access token for refresh and upgrade details.

Manage local users

Local users are accounts with a password, stored in LEA Platform itself. Once SSO is on, people should not use them day to day.

There are two account types:

Account typeSigns in to the console?Use it for
Local user (break-glass)Yes while SSO is off; with SSO on, only during a break-glass windowThe first admin, and one emergency admin account kept disabled
API accountNeverIntegrations that cannot use tokens, for example a reporting tool that only supports user name and password. Limited to the endpoints you list

Create or edit a local user

  1. Open Settings → Local users.
  2. Click + Create new user below the table, or click a user to edit it.
  3. Fill in Username.
  4. Pick the Role and, if you want, a Scope (see Give a local user a role and scope).
  5. Pick the Account type: Local user (break-glass) or API account.
  6. Type a Password of at least 12 characters. When editing, leave it empty to keep the current password.
  7. Turn on Disabled to keep the account switched off (recommended for break-glass accounts while SSO is on).
  8. For an API account, under Allowed endpoints, click Add endpoint for each call it may make: pick the Methods and type the Path. A path may end with *, for example /api/latest_cmd_results_all*. Everything else is refused.
  9. Click Save at the top right.

You should see the user in the list with its type and state (Enabled, DISABLED or BREAK-GLASS OPEN).

ColumnWhat it shows
RoleWhat the account may do: one of the built-in roles, the same ones you give to people through single sign-on.
ScopeThe host groups the account is limited to, or Everything when it is not limited.
TypeWhether the account signs in to the console (Local user) or only calls the listed API endpoints with its password (API account).
StateWhether the account can sign in now: Enabled, DISABLED, or BREAK-GLASS OPEN while an emergency window is open on the server.
Last sign-inWhen this account last signed in to the console with its password. Calls to the API do not count.

The copy icon at the top right of a user clones it; the delete icon removes it after you confirm.

Note: After 5 wrong passwords an account is locked for 15 minutes. Failed sign-ins raise a notification.

Warning: While SSO is on, LEA Platform warns about every enabled local user and API account (yellow dots in Settings and a notification). Keep local users disabled unless you are using them.

An API account calls the API with Basic authentication, for example:

curl -u powerbi:'the-account-password' https://lea.example.com/api/latest_cmd_results_all

Replace powerbi with the account's Username, the password with its password, and lea.example.com with your LEA server address.

Give a local user a role and scope

Local users and API accounts use the same roles and host-group scopes as people who sign in with SSO. For example, a reporting tool can be a Viewer of the Linux-Prod group only, or a ticketing system an Operator of the Helpdesk group.

  1. Open Settings → Local users and click the user.
  2. Pick the Role, for example Viewer, Auditor or Operator.
  3. To limit the account to some host groups, pick them under Scope. Leave it empty for everything.
  4. Click Save at the top right.

You should see the role and the scope groups in the user list. The account sees and acts on hosts in those groups only, in the console, the REST API and the custom API. An API account's Allowed endpoints still apply on top of the role.

Some roles cannot be limited to groups, because they include settings that always apply to everything: Engineer, Auditor and Administrator. The Scope field is greyed out for them.

Important: Keep your break-glass recovery account a global Administrator (no scope). If you save the last global Administrator local user with a lesser role, a scope, or as an API account, LEA Platform saves it and shows a warning: you would have no local account left to recover full access with. A disabled account still counts, because a break-glass window opens it.

Local users also appear in Settings → Access on the Bindings tab (source LOCAL), and you can check what they can do on the Effective access tab.

Open a break-glass window

Break-glass is emergency console access with a local account while SSO is on, for example when the identity provider is down. It is opened from the LEA server, not from the console, so a stolen password alone is not enough.

  1. Log in to the LEA server and go to the release directory:

    cd /opt/lea/lea_release
    
  2. Open a window for the local account (here admin) for 60 minutes:

    ./lea_ha.sh breakglass on admin --minutes 60
    

    You should see: "sign in at https://…/login with 'Sign in with a local account'". The account works during the window even if it is disabled.

  3. Open the sign-in page, click Sign in with a local account, and sign in with the user name and password.

  4. When you are done, close the window:

    ./lea_ha.sh breakglass off admin
    

Check open windows with ./lea_ha.sh breakglass status. The window can last at most Break-glass maximum (minutes) (Policy tab). Opening, using and closing a window raises a critical notification, and when it ends the account's sessions end.

Your own account

Open My account from the Welcome, <your name> button at the top right → Account settings. The left list has these sections:

SectionWhat you do there
NotificationsPick a notification profile, choose what reaches you on each channel, quiet hours, desktop alerts. See Notifications.
Email, Slack & TeamsConnect your own email, Slack or Teams account and set a digest.
MutedNotifications you silenced, and for how long.
Saved preferencesAuto refresh, rows per page, and choices this browser remembers (tables, filters, AI conversations). Clear or Clear all restores the defaults.
Command lineInstall the lea command and see the terminals signed in as you.
PasskeysAdd or remove the passkeys you use to confirm it is you. See Passkeys.
Tokens and accessYour personal access tokens, temporary access and your requests waiting for approval.

Note: There is no password change in My account. SSO users change their password at their identity provider. An administrator changes a local user's password in Settings → Local users.

Confirm it is you (re-authentication)

Some changes are sensitive enough that LEA Platform asks you to prove again that you are at the keyboard. A dialog titled Confirm it is you appears when you:

  • upload, approve or delete a function, or change its secrets or the function policy (Settings → Functions);
  • create a personal access token with Manage functions or Manage the platform;
  • change the security policy (Settings → Security);
  • do anything your administrator turned on in Settings → Security, for example run an ad-hoc command, roll out a rule update or remove results. This includes actions you approve in the AI assistant.

After you confirm, the action you started continues by itself. Click Cancel and nothing changes; you see "Confirmation cancelled".

What to do:

  • Passkey (if you added one): click Use passkey and confirm with Touch ID, Windows Hello, your phone or your security key. The action then continues.
  • Local account: type your Password and click Confirm. The confirmation stays valid for 10 minutes on this session.
  • SSO account: click Re-authenticate. Your identity provider asks you to sign in again, then you come back to the same page. Repeat the action you were doing.

Some identity providers, such as Google, cannot prove that you just signed in again, so Re-authenticate is not offered for them. With such a provider, add a passkey and use it here. Until you have one, the dialog explains how to add it.

If your administrator set the method to Passkey only, only Use passkey is offered. Without a passkey the dialog says "This action needs a passkey and you have none yet." Add one under My account → Passkeys and repeat the action.

Why: if someone walks up to an unlocked browser, they still cannot change code that runs on your server. Wrong passwords count towards the account lock.

If you sign in at the identity provider as a different person, you see "You signed in as a different identity. Re-authenticate as the same person."

Require confirmation for sensitive actions

Administrators choose which actions need Confirm it is you in Settings → Security. One confirmation covers every protected action for 10 minutes on that browser session.

  1. Open Settings → Security.
  2. Under Confirmation method, pick:
    • Any method: password (local users), a fresh sign-in at the identity provider, or a passkey.
    • Passkey only: Touch ID, Windows Hello, a phone or a security key. Add a passkey to your own account first; otherwise saving shows "Add a passkey to your own account (My account → Passkeys) before requiring passkeys". People without a passkey cannot do protected actions until they add one.
  3. Under Protected actions, turn each action on or off. Reset to defaults turns the recommended ones back on.
  4. Click Save. Saving always asks you to confirm it is you.

You should see: "Security policy saved."

ActionWhat it coversDefault
FunctionsUpload, approve or delete functions, their secrets and policy, tokens with Manage functionsAlways on
Security policyConfirmation method and protected action listAlways on
Ad-hoc commandsRun a command on a host (Terminal tab or the AI assistant)On
Rule changesCreate, edit or delete rules, their commands, parameters and functionsOn
Rule updates and rolloutApply rule updates, promote or pin versions, the rollout defaultOn
Rule packs and sourcesImport rule packs, add rules from the catalog, manage rule sourcesOn
Agent updatesImport agent versions, change the fleet default agent version, pin agent versions to hosts or groupsOn
GroupsCreate, edit or delete groups, their hosts and rulesOff
Remove resultsDelete rule resultsOn
Remove or re-enroll hostsDelete hosts or force them to enroll againOn
Users and accessLocal users, custom roles and grants, access requests, converting an API accountOn
Sign-in and identity providersSign-in policy, identity providers, role mappings, SCIM tokensOn
API, CLI and deployment tokensCreate personal access tokens, approve a lea sign-in, create or rotate deployment tokens, create and change service accountsOn
ApprovalsApprove or reject requests of other people, including temporary accessOn
Cluster and TLSJoin tokens, promote, switch over, remove nodes, the TLS certificateOn
Compliance settings and signing keyFrameworks and the evidence signing keyOn
Webhooks and integrationsWebhooks, email/Slack/Teams connections and team routesOff
AI assistant settingsProvider, model and keysOff
System settingsRetention, audit log purge, backupsOff
LicenseUpload a licenseOff

Signing someone out, revoking a token or denying a lea sign-in is never protected, so you can react fast during an incident.

Personal access tokens (the lea command, scripts, MCP clients) cannot answer the dialog, so the policy does not apply to them. Their scopes still limit what they can do: changes to users, sign-in, tokens and the cluster need a token with Manage the platform (for the lea command: lea login --platform). Creating a token or approving a lea sign-in is itself protected. Every confirmation and policy change is in the audit log.

Passkeys

A passkey lets you confirm it is you with Touch ID, Windows Hello, your phone or a security key, instead of typing a password or signing in again at your identity provider. It works with every sign-in method, and it is the only way to confirm when your identity provider (for example Google) cannot.

Add a passkey

  1. Open My account → Passkeys.
  2. Click Add passkey.
    • If you signed in within the last 10 minutes, or confirmed it is you within the last 10 minutes, the Add a passkey dialog opens.
    • Otherwise Confirm it is you opens first. If it offers no way to confirm (no passkey yet and an identity provider like Google), sign out, sign in again and add the passkey within 10 minutes.
  3. Type a Name you will recognise, for example "MacBook Touch ID", and click Create passkey.
  4. Follow your browser's prompt: touch the fingerprint sensor, enter your device PIN, scan the code with your phone or touch your security key.

You should see: "Passkey added." and the passkey in the list with the type This device, Phone or tablet or Security key.

You can add up to 10 passkeys, for example one per computer plus a security key as a spare. Each one sends you a notification Passkey added or removed, and the change is in the audit log.

Remove a passkey

Click Remove next to it. Removing also needs a sign-in or confirmation within the last 10 minutes. Lost the device? Sign out, sign in again, then remove it within 10 minutes and add a new one.

Columns

ColumnMeaning
PasskeyThe name you gave it
TypeThis device (built into the computer), Phone or tablet, or Security key
AddedWhen you added it
Last usedWhen you last confirmed with it, or Never

If it does not work

  • "The passkey prompt was cancelled or timed out." You closed the browser prompt or waited too long. Click again.
  • "This device already has a passkey for your account." Use the existing one, or remove it first.
  • "The passkey request expired. Try again." More than 5 minutes passed since the dialog opened. Open it again.
  • "The passkey could not be verified" or "This passkey is not registered to your account": you picked a passkey from another account or another LEA Platform server. Pick the right one. Failed attempts count towards the sign-in lock for your address.
  • "This browser does not support passkeys." Use a current Chrome, Edge, Safari or Firefox.
  • A passkey works only on the address you added it on (for example https://lea.example.com). After the console moves to a new address, add new passkeys.

Create a personal access token

A personal access token (starts with lea_pat_) lets a script, a CI job or an AI tool call LEA Platform as you.

  1. Open My account → Tokens and access and click Create token. Administrators can also use Settings → AI Assistant → Personal access tokens → Create Token, which also shows ready-made MCP client settings.

  2. Type a Name that says where it is used, for example Open WebUI or CI functions.

  3. Pick Expires: 30 days, 90 days, 180 days or 1 year (never longer than Token maximum lifetime (days)).

  4. Choose the scope:

    Option in the dialogWhat the token can doWho can choose it
    (no box ticked)Read onlyEverybody
    Allow write tools …Read and write, including AI write tools over MCPAdministrators
    Manage functions: upload, approve, delete, secrets and policy …Everything above plus function uploads, approvals, secrets and policy (for CI and the lea CLI)Administrators, after Confirm it is you
    Manage the platform (users, sign-in, tokens, cluster) …Read and write plus changes to users and access, single sign-on, tokens and the cluster (scope platform)Administrators, after Confirm it is you
  5. Optionally limit the token under Limit this token (optional) to some permissions and host groups. See Narrow a token.

  6. Click Create.

  7. Copy the token now. You should see "This token is shown only once. Copy it now."

  8. Click Done.

To revoke a token, click Revoke in My account → Tokens and access, or its revoke icon in Settings → AI Assistant. Administrators can turn on Show tokens of all users there to see and revoke everybody's tokens.

Tip: For an integration that runs without you (SIEM, CMDB, CI), create a service account instead. Its tokens do not stop when you leave or change role.

Important: A token stops working when it expires, when it is revoked, when its owner is disabled, or (SSO users) when its owner has not signed in to the console for Token owner inactivity (days).

For SSO users, personal access tokens and command-line sign-ins also pause when the identity provider's stored role and group details are older than Token claim freshness (hours) in Settings → Single sign-on → Policy (24 hours by default). The request returns 401 and asks you to sign in again. Sign in to the console to resume your token if you still have access. Using the token does not renew this time limit. A console session refresh renews it only when the identity provider supplies a new ID token. Application identities and local accounts keep their existing behavior.

After upgrading to this policy, existing SSO token owners have a one-time 24-hour grace period to sign in. Other token checks still apply. Plan for this before upgrading so scripts do not stop unexpectedly after the grace period ends.

An identity provider refresh denial or back-channel sign-out ends console sessions without revoking personal access tokens or renewing their freshness. SCIM group removal takes effect on the next token request: another role mapping or grant may still allow access. A role or group removed only at the identity provider may remain in stored details until fresh claims arrive or the freshness limit expires. For unattended integrations, use a service account or an application identity rather than a person's token; see Application identities.

Sign in from the command line

The lea command line tool gets its own token by asking you to approve it in the console.

  1. Install it from your own LEA server. The exact commands for your server are in My account → Command line:

    curl -fsSL https://lea.example.com/deploy/install-lea-cli.sh | LEA_SERVER=https://lea.example.com sh
    
  2. Sign in:

    lea login --server https://lea.example.com
    

    Your browser opens the page Sign in to the LEA CLI. Sign in as usual, check Machine, System and From address, then choose:

    • Access: Read only or Read and write. Only administrators can pick Read and write.
    • Expires: how long the terminal stays signed in, from 1 day up to the maximum your administrator allows. The default is the token default lifetime.
    • Manage the platform (users, sign-in, tokens, cluster): shown only when the terminal ran lea login --platform. Only administrators can leave it ticked, and Approve then asks you to Confirm it is you.

    Click Approve (or Deny if you did not start this yourself).

    You should see: a LEA Platform CLI is signed in page with the server, who you are signed in as, the access, the expiry, the machine and the profile. Return to your terminal and close the tab.

  3. On a server without a browser, use a one-time code instead:

    lea login --server https://lea.example.com --device
    

    The CLI shows a code such as QGTQ-SCNC. Open https://lea.example.com/cli/activate on any device, type it into Code, click Continue, then Approve.

  4. Check it worked with lea whoami.

  5. To manage users, sign-in, tokens or the cluster from the terminal (for example lea deploy-tokens create), administrators sign in with --platform:

    lea login --platform
    

    Without it these commands stop with "Sign in again with lea login --platform".

Replace lea.example.com with your LEA server address. Administrators get read and write access unless they add --read-only or pick Read only on the approval page; everybody else gets read access. Each terminal appears under My account → Command line with its system, CLI version and expiry; click Sign out there if a machine is lost. lea logout signs the terminal out from the terminal itself.

ColumnWhat it shows
TerminalThe user and machine name (user@host) where lea login was run.
SystemThe operating system and processor type of the machine where lea login was run, for example linux / amd64.
READ & WRITEThis command-line sign-in can view and change things, as far as your own role allows.
READ ONLYThis command-line sign-in can only view; it cannot change anything.

Note: The token from lea login cannot upload or approve functions. For that, create a token with Manage functions (see Create a personal access token) and use lea login --token - or the LEA_TOKEN variable. More in the CLI reference.

If you are locked out

Find your situation in this table first.

SituationFix
"The account is locked after repeated failures. Try again later."Wait 15 minutes. The lock lifts by itself.
SSO is on and the identity provider is down or misconfiguredOpen a break-glass window for a local admin, fix the provider, close the window.
You can sign in with SSO but get "You do not have access…" and no admin can sign inOpen a break-glass window, then fix the role mappings or approve your access request.
The only local admin's password is lostReset a local password on the server.
A local user forgot the password, and another admin can sign inThat admin edits the user in Settings → Local users and types a new Password.

Reset a local password on the server

Use this only when no administrator can sign in. You need a shell on the LEA server with Docker access. In a cluster, run it on the node that holds the primary database.

  1. Go to the release directory:

    cd /opt/lea/lea_release
    
  2. Create a password hash. The command asks for the new password (at least 12 characters) without showing it, and prints a line starting with $2b$:

    docker compose exec api python3 -c 'import bcrypt, getpass; print(bcrypt.hashpw(getpass.getpass("New password: ").encode(), bcrypt.gensalt()).decode())'
    
  3. Store it for the user admin and unlock the account. Replace PASTE_HASH_HERE with the printed line. Keep the single quotes exactly as shown:

    docker compose exec db psql -U lea -d lea -c 'UPDATE users SET password=$lea$PASTE_HASH_HERE$lea$, failed_attempts=0, locked_until=NULL WHERE name=$lea$admin$lea$;'
    

    You should see UPDATE 1. UPDATE 0 means there is no local user with that name.

  4. If SSO is on, open a break-glass window for admin. If SSO is off, sign in directly.

Warning: This writes directly to the database. Type the user name carefully, and do not run any other SQL. Every later sign-in is audited as usual.

If something goes wrong

SymptomFix
The sign-in page shows no SSO buttonNo provider is enabled. Open the provider and turn on the switch at the top of the dialog.
"The identity provider refused the sign-in"The redirect URI or the credential does not match. Compare the URLs under Register in your identity provider and run Run test.
"The identity provider cannot be reached right now"The LEA server cannot reach the provider. Check DNS and firewall, or set Backend URL and CA certificates (PEM).
"The sign-in took too long or the link was already used"Start the sign-in again within 10 minutes, in one browser tab.
People lose their role after a few minutesTheir group or app role was removed at the identity provider, or the mapping value is wrong. Check the Identities tab.
A script gets password_disabledSSO is on. Turn the account into an API account, or use a personal access token.
A script gets not_allowedThe API account called an endpoint that is not in Allowed endpoints.
The CLI says it needs the functions scopeUse a personal access token with Manage functions.
A script or lea gets platform_scope_requiredChanges to users, sign-in, tokens or the cluster need a personal access token with Manage the platform, or for the lea command lea login --platform.

More symptoms are in Troubleshooting and the sign-in reference.