Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,952
Community Members
 
Community Events
176
Community Groups

Crowd - Sun Directory Server - No Permission for Self-Service LDAP Password Update

I have Crowd 2.3.2 deployed on a CentOS 6 server using the Embedded Database.

I currently added a Sun Directory Server using the LDAP Connector.

The LDAP Server Users are synched.

If I log into Crowd using the Self-Service of an LDAP user and proceed to Change Password a message is displayed stating:

You do not have permission to change your password.


On the Sun Directory Server I have indicated in the Password Policy that users can change their password.

On the Crowd side I have set the Sun Directory Server Connector as follows:

Type: Sun Directory Server Enterprise Edition

URL: ldap://my.server.com:389/

Base DN: dc=my,dc=server,dc=com

I am not sure what else is needed?

1 answer

1 accepted

1 vote
Answer accepted

Hi there,

I see that you are connecting to the LDAP using the ldap protocol, instead of ldaps (URL: ldap://my.server.com:389), as per what I know you need an SSL connection to perform password changes into the LDAP (it seems to be a restriction from the LDAP server, not Crowd itself).

You may try setting your LDAP directory in Crowd over SSL and see if it solves this issue. You can use this documentation as a guide line for this configuration.

Cheers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events