Directory / LDAP login

Many tools predate OIDC and SAML but can authenticate against an LDAP directory. For these, ResorsIT does not need a browser SSO redirect: the tool binds to the platform directory and checks the user’s login there, so the credential is still centrally held and centrally governed.

LDAP is a genuine platform access method, not a fallback bookmark. The account lives in one place, is disabled in one place, and the tool reads it live.

How ResorsIT integrates it

• The platform exposes an LDAP endpoint – the IdP’s LDAP outpost, or the platform directory service – that tools can bind against
• The tool authenticates each login against that directory
• Group membership in the directory can drive the tool’s roles and access
• Deactivating the user in the platform disables the LDAP login everywhere at once, without touching each tool

When a tool uses this

Directory login fits tools whose only central-identity option is LDAP (or Active Directory): older on-prem applications, network appliances, mail and file services, and anything that lists “LDAP / AD authentication” but not OIDC/SAML. Each tool page records LDAP support in its SSO facet alongside OIDC, SAML, and SCIM.

Where a tool speaks both, single sign-on is the richer path and takes precedence. Where a tool cannot bind to a directory but its account lifecycle can still be automated, see provisioned account.