I have a confluence server that authenticates against an OpenLDAP server. This is working fine, it obeys the groups, obeys the users, lets users change their password, etc.
This is also where the problem comes in, when changing passwords it doesn't seem to be behaving the same way a ldappasswd command would, it is allowing users to override the password policy for instance (length, complexity). Those are being enforced when I run ldappasswd or passwd on a general linux machine.
I assume this is happening because the query is being executed as the bind user, which has access to change the userPassword field without going through the pwpolicy module.
Is there a way to have Confluence bind as the user vs the binddn for password changes? That should fix that problem.
I don't think that this is currently possible. The simplest workaround would be to use a bind user that can not bypass the pwpolicy module. Long term, it may be best to file a suggestion against Confluence and Crowd for this.
I attended Atlassian Summit 2019 and learned a lot from the presenters, attendees and knowledgeable Atlassian product managers. The presentations I attended focused on applying Agile, pla...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events