Repository navigation
Directory sign in Entra ID AD LDAP SCIM
Administration · Hrvatski · Administrators only
Let people sign in with Microsoft Entra ID, Okta, Google or any OpenID Connect provider, or LDAP/Active Directory, and provision with SCIM.

Admin panel → Directory sign-in.
- Add a provider and choose its kind; the editor says where to create the client there.
- Register the redirect address shown (
https://<WRM>/api/auth/oidc/callback). - Enter the issuer, client ID and secret; Test connection checks every step.
-
Rules map a claim (
roles,groups,hd…) to a WRM role and teams. Without rules only linked accounts may sign in.
Add directory: kind (Active Directory or other LDAP), ldaps:// server (or ldap:// with StartTLS), a service account that may read users and groups, the user and group base, and rules from groups to roles. Test signs in a user of your choice.
Entra ID or Okta can create, change and disable WRM accounts automatically: SCIM → New token, then give the address and token to the directory.
Directory users cannot sign in with a local password unless you allow it; the break-glass administrator always can.
Search terms: sso, single sign-on, oidc, openid, entra, azure ad, active directory, ad, ldap, adfs, okta, keycloak, google workspace, scim, groups, domain, provisioning
The same article is in WRM: ? in the top bar (or F1) opens Help, where you can search it and ask the help AI.
← Previous: Security levels and posture · Home · Next: Audit log, recordings, SIEM and lockdown →
WRM PRO v14.14.1 · generated from the in-app help on every release · screenshots use invented demo data · Repository · Issues
Quick start · What's new · Comparison