This page can now be found at: https://clazzes.atlassian.net/l/c/HCvtdui8
The LDAP login service authenticates against users in an ADS domain or against users in an LDAP server configured for an individual domain.
tryLogin() needs credentials if run against a legacy LDAP Server.
For AD DS servers, an additional non-search authentication method
bindAds is implemented for
tryLogin(), which tries to bind using a principal in the form
getGroupMembers() need bind credentials and will only work in AD DS environments.
The following sample configuration is the most common configuration OSGi configuration in PID
org.clazzes.login.ldap, which allows you to authenticate users against an Active Directory Domain.
All you need to know is the Windows/NetBIOS Name of your domain and the corresponding DNS name used to physically locate the Active Directory server.
In our example we use
EXAMPLE as the Windows/NetBIOS domain name with its DNS counterpart
The LDAP login service may be configured using the OSGi configuration PID
org.clazzes.login.ldap using these configuration values:
|The domain to use for principals, which do not contain a domain.|
|The server to contact. Supported URL schemes: |
|The method for authenticating a user. Supported methods: |
|The DN used for binding before searching something in the domain <domain>. For |
|The password used for binding searching something in the domain <domain>. For |
|The LDAP attribute to use for finding a given user name.|
|The LDAP attribute to try to use as pretty name for users and groups.|
|The LDAP attribute to try to use as primary e-mail address for users.|
|The LDAP attribute to try to use as mobile phone number for users. This number is used to send ephemerals OTP for two-factor-authentication to the user. If this option is activated, two-factor signons are mandatory for this domain. Usually, this option is configured to the value |
|The LDAP attribute to try to use as a space separated list of 12-character YubiKey token IDs (like |
There may be multiple domains in a configuration.
The URL schemes for a domain controller are ldap, ldaps and ads.
ads URL scheme for the URL
ads://mydomain.com undertakes a lookup for the DNS records
to auto-detect the apropriate
When directly specifying the LDAP-Server using an URL like
ldap://ldap-01.mydomain.com it is possible to specify the baseDN for searches using a pseudo-path like in
I some software product has pointed to this page for configuration details, the bundle is probably already installed in the OSGi container the software product runs in.
OSGi administrators maintaining an individual OSGi container can install the ldap-login-service bundle using these osgi commands:
The maven artifact is: