Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
+1
person also asked this
people also asked this
Replies
2 replies
Subscribers
8 subscribers
Views
1257 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Hi all, Could anyone please let me know where I did the mistake in configuring t
sikhivahans
over 11 years ago
Hi all, Could anyone please let me know where I did the mistake in configuring the ldap?
Let us suppose that there is an ldap server at port 389 like this : LDAP://appianldap:389/DC=sampleDC,DC=com.
Assume that there is a user by name "User1" with password as "User@123" in ldap directory. Here User1 have all privileges. Is this configuration fine or do I need to do anything apart from this?
<bean id="contextSource" class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">
<property name="userDn" value="cn=User1,dc=sampleDC,dc=com"/>
<property name="password" value="User@123"/>
</bean>
In documentation it is mentioned that we need to provide "manager DN" credentials here. What do manager DN mean?
Also could anyone please let me know what is the role played by "userSearch" bean? Even I am seeing an error numbered 712 in the console relating to the spring framework. Could anyone let me know the reason for this?...
OriginalPostID-73347
OriginalPostID-73347
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 11 years ago
The userDn/password in the DefaultSpringSecurityContextSource bean are the credentials of a user authorized to bind to and search for other users in the LDAP server.
In regards to your question about the userSearch bean of type FilterBasedLdapUserSearch; this bean uses an LDAP filter to match the user object in the directory. The only valid parameter is {0} which will be replaced with the user's login name. This bean receives three arguments in its constructor through this configuration file:
constructor-arg 0: search base (where to start the search from). Not required if the search base was specified in the LDAP server URL.
constructor-arg 1: searchFilter. Make sure the right field is used. Most of the times you will use CN or sAMAccountName
If a more complex filter is required, it will be passed here as explained in the documentation, for instance:
<constructor-arg index="1" value="(&(sAMAccountName={0})(memberof=CN=appianUsers,OU=Groups,OU=BPM,DC=appian,DC=corp))"/>
constructor-arg 2: contextSource (this is the bean that contains the credentials used to bind to the LDAP server)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 11 years ago
The userDn/password in the DefaultSpringSecurityContextSource bean are the credentials of a user authorized to bind to and search for other users in the LDAP server.
In regards to your question about the userSearch bean of type FilterBasedLdapUserSearch; this bean uses an LDAP filter to match the user object in the directory. The only valid parameter is {0} which will be replaced with the user's login name. This bean receives three arguments in its constructor through this configuration file:
constructor-arg 0: search base (where to start the search from). Not required if the search base was specified in the LDAP server URL.
constructor-arg 1: searchFilter. Make sure the right field is used. Most of the times you will use CN or sAMAccountName
If a more complex filter is required, it will be passed here as explained in the documentation, for instance:
<constructor-arg index="1" value="(&(sAMAccountName={0})(memberof=CN=appianUsers,OU=Groups,OU=BPM,DC=appian,DC=corp))"/>
constructor-arg 2: contextSource (this is the bean that contains the credentials used to bind to the LDAP server)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data