Skip to Content

Changes for page org.clazzes.login.ldap

Last modified by wolfgang_glas@iteg_at on 2018-08-25 09.26:23
From version 6.1
edited by christoph_lechleitner@iteg_at
on 2014-01-03 04.05:26
Change comment: Restructuring to avoid confusing product admins
To version 1.1
edited by christoph_lechleitner@iteg_at
on 2012-10-04 02.13:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,21 @@
1 -= {{id name="org.clazzes.login.ldap-Functionality"/}}Functionality =
1 +The ldap-login-service is provided as an OSGi bundle, which may be activated by
2 2  
3 -
3 +(% class="code" %)
4 +(((
5 +obr:addurl http:~/~/maven.clazzes.org/repository.xml
6 +obr:deploy ldap-login-service
7 +)))
4 4  
9 +The maven artifact is:
10 +
11 +(% class="code" %)
12 +(((
13 +<groupId>org.clazzes.login</groupId>
14 +<artifactId>ldap-login-service</artifactId>
15 +)))
16 +
17 +=== {{id name="org.clazzes.login.ldap-Functionality"/}}Functionality ===
18 +
5 5  The LDAP login service authenticates against users in an ADS domain or against users in an LDAP server configured for an individual domain.
6 6  
7 7  The function {{code language="none"}}tryLogin(){{/code}} needs credentials if run against a legacy LDAP Server.
... ... @@ -10,55 +10,8 @@
10 10  
11 11  The functions {{code language="none"}}searchUser(){{/code}}, {{code language="none"}}getGroups(){{/code}}, {{code language="none"}}getGroupMembers(){{/code}} need bind credentials and will only work in AD DS environments.
12 12  
13 -= {{id name="org.clazzes.login.ldap-SampleConfigurationforauthenticationagainstanADS-Domain"/}}Sample Configuration for authentication against an ADS-Domain{{id name="org.clazzes.login.ldap-sampleAdsConfig"/}} =
27 +=== {{id name="org.clazzes.login.ldap-Configuration"/}}Configuration ===
14 14  
15 -The following sample configuration is the most common configuration OSGi configuration in PID {{code language="none"}}org.clazzes.login.ldap{{/code}}, which allows you to authenticate users against an Active Directory Domain.
16 -
17 -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.
18 -
19 -In our example we use {{code language="none"}}EXAMPLE{{/code}} as the Windows/NetBIOS domain name with its DNS counterpart {{code language="none"}}example.com{{/code}}.
20 -
21 -|=(((
22 -(% class="tablesorter-header-inner" %)
23 -(((
24 -Key
25 -)))
26 -)))|=(((
27 -(% class="tablesorter-header-inner" %)
28 -(((
29 -Value
30 -)))
31 -)))
32 -|(((
33 -{{code language="none"}}
34 -defaultDomain
35 -{{/code}}
36 -)))|(((
37 -{{code language="none"}}
38 -EXAMPLE
39 -{{/code}}
40 -)))
41 -|(((
42 -{{code language="none"}}
43 -domain.EXAMPLE.controllerUri
44 -{{/code}}
45 -)))|(((
46 -{{code language="none"}}
47 -ads://example.com
48 -{{/code}}
49 -)))
50 -|(((
51 -{{code language="none"}}
52 -domain.EXAMPLE.authMethod
53 -{{/code}}
54 -)))|(((
55 -{{code language="none"}}
56 -bindAds
57 -{{/code}}
58 -)))
59 -
60 -= {{id name="org.clazzes.login.ldap-DetailedConfiguration"/}}Detailed Configuration =
61 -
62 62  The LDAP login service may be configured using the OSGi configuration PID {{code language="none"}}org.clazzes.login.ldap{{/code}} using these configuration values:
63 63  
64 64  |=(((
... ... @@ -146,17 +146,6 @@
146 146  )))|(((
147 147  The LDAP attribute to try to use as pretty name for users and groups.
148 148  )))
149 -|(((
150 -{{code language="none"}}
151 -domain.<domain>.eMailAddressAttribute
152 -{{/code}}
153 -)))|(((
154 -{{code language="none"}}
155 -mail
156 -{{/code}}
157 -)))|(((
158 -The LDAP attribute to try to use as primary e-mail address for users.
159 -)))
160 160  
161 161  There may be multiple domains in a configuration.
162 162  
... ... @@ -174,26 +174,4 @@
174 174  
175 175  to auto-detect the apropriate {{code language="none"}}ldap(s){{/code}} URI.
176 176  
177 -= {{id name="org.clazzes.login.ldap-ManualinstallationinOSGicontainer"/}}Manual installation in OSGi container =
178 -
179 -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.
180 -
181 -OSGi administrators maintaining an individual OSGi container can install the ldap-login-service bundle using these osgi commands:
182 -
183 -(% class="code" %)
184 -(((
185 -obr:addurl http:~/~/maven.clazzes.org/repository.xml
186 -obr:deploy ldap-login-service
187 -)))
188 -
189 -= {{id name="org.clazzes.login.ldap-Developerinformation"/}}Developer information =
190 -
191 -The maven artifact is:
192 -
193 -(% class="code" %)
194 -(((
195 -<groupId>org.clazzes.login</groupId>
196 -<artifactId>ldap-login-service</artifactId>
197 -)))
198 -
199 199  
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -688760
1 +688896
URL
... ... @@ -1,1 +1,1 @@
1 -https://clazzes.atlassian.net/wiki/spaces/LOGIN/pages/688760/org.clazzes.login.ldap
1 +https://clazzes.atlassian.net/wiki/spaces/LOGIN/pages/688896/org.clazzes.login.ldap