The ldap-login-service is provided as an OSGi bundle, which may be activated by
obr:addurl http://maven.clazzes.org/repository.xml
obr:deploy ldap-login-service
The maven artifact is:
<groupId>org.clazzes.login</groupId>
<artifactId>ldap-login-service</artifactId>
Functionality
...
Functionality
The LDAP login service authenticates against users in an ADS domain or against users in an LDAP server configured for an individual domain.
...
The functions searchUser(), getGroups(), getGroupMembers() need bind credentials and will only work in AD DS environments.
Sample Configuration for authentication against an ADS-Domain
| Anchor | ||||
|---|---|---|---|---|
|
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.
...
Key | Value |
|---|---|
defaultDomain | EXAMPLE |
domain.EXAMPLE.controllerUri | ads://example.com |
domain.EXAMPLE.authMethod | bindAds |
Detailed Configuration
The LDAP login service may be configured using the OSGi configuration PID org.clazzes.login.ldap using these configuration values:
...
to auto-detect the apropriate ldap(s) URI.
Manual installation in OSGi container
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:
obr:addurl http://maven.clazzes.org/repository.xml
obr:deploy ldap-login-service
Developer information
The maven artifact is:
<groupId>org.clazzes.login</groupId>
<artifactId>ldap-login-service</artifactId>