Option A (cloud-friendly): SSO via Azure AD / Okta
Add an SSO module (OIDC or SAML) from the Marketplace.
Configure your IdP (Azure AD/Entra ID, Okta, ADFS).
Map a claim (UPN or sAMAccountName) to the Mendix account name.
On login, $CurrentUser
will be the real user; display it anywhere.
Pros: works in Mendix Cloud, standard, secure.Cons: needs IdP setup.
Option B (on-prem with IIS): Windows Auth (Kerberos/NTLM) pass-through
In IIS: enable Windows Authentication, disable Anonymous for your site/reverse proxy.
Configure ARR/URL-Rewrite to forward a header with the Windows user, e.g.X-Remote-User: {REMOTE_USER}
In Mendix: use a Request-Header Authentication module/microflow to read X-Remote-User
, auto-create/lookup the Account, and log in.
Pros: true “domain\user” without a login screen on intranet.Cons: IIS required; only suitable for internal networks/browsers that allow IWA
Hi Felix,
Mendix by itself doesn’t know about the Windows system user, it only knows about the Mendix session user $currentUser. That’s why you see Anonymous
If you want the domain user ( domain\sysuser ), you need to integrate with the identity provider that authenticates Windows logins you can try SAML, OIDC.
Regards
Guna P