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
Replies
5 replies
Subscribers
5 subscribers
Views
1679 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Hello, Iam try to integrate APPIAN 7.4 with LDAP 2003, We have created a gr
vineetl876
over 10 years ago
Hello,
Iam try to integrate APPIAN 7.4 with LDAP 2003, We have created a group in LDAP, and added the SA. But iam getting badcredentials exception. Let me know if anything is missing.
My configuration is mentioned below:
<constructor-arg value="ldap://corp.name.net:389/DC=corp,DC=name,DC=net"/>
<property name="userDn" value="Sa-Appian"/>
<property name="password" value="test123"/>
</bean>
<bean id="userSearch_lds" class="org.springframework.security.ldap.search.FilterBasedLdapUserSearch">
<constructor-arg index="0" value=""/>
<constructor-arg index="1" value="(&(sAMAccountName={0})(memberof=OU=Appian_Users,DC=corp,DC=name,DC=net))"/>
...
OriginalPostID-100824
OriginalPostID-100824
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 10 years ago
If you are getting this error:
Authentication request failed: org.springframework.security.authentication.BadCredentialsException: Bad credentials
this means you haven't created the user in Appian. Remember that accounts have to exist beforehand (the password is not relevant since Appian will authenticate against your LDAP server but the account needs to exist in Appian first).
For example, if a user types: "eduardoFuentes" as the user then there should be an account both in LDAP and in Appian (people tab) with that exact name for the authentication to succeed, otherwise Appian will get the "good to go" from LDAP but when it tries to see if there's a user inside Appian with that username, if not present, a BadCredentialsException is thrown.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineetl876
over 10 years ago
Eduardo,
The user is already present in APPIAN, for example, Vineet Kumar, and SAM Account is : a28123, the same a28123 is also created in APPIAN, but still the same error is thrown.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Then what could be wrong is the password for the service account. It's better to test this outside Appian first to make sure you can bind the SA to your LDAP server. There are several tools available online, one example is JXplorer
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineetl876
over 10 years ago
I have tested this using SOfterra LDAP, and it is working for SA account, Is this something related to SA permissions, or do we need to create a group in LDAP of type CN under OU. Is it something permissions issue.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Keep in mind that:
1. If this is an LDAP directory the syntax for the userDN is of type;
<property name="userDn" value="cn=Sa-Appian,dc=corp,dc=name,dc=net"/>
2. If this is active directory the syntax for the userDN is of type:
<property name="userDn" value="Administrator@appiancorp.com"/>
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel