Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot change LDAP password on Synology NAS #338

Open
db4 opened this issue May 24, 2017 · 0 comments
Open

Cannot change LDAP password on Synology NAS #338

db4 opened this issue May 24, 2017 · 0 comments

Comments

@db4
Copy link

db4 commented May 24, 2017

I have a problem with pGina 3.2.4.0/Synology DSM 6.1 (probably related to #323): pGina silently fails to change LDAP password on Synology OpenLDAP server. Network sniffer shows that pGina issues request

Lightweight Directory Access Protocol
    LDAPMessage modifyRequest(4) "uid=xxxx,cn=users,dc=ldap,dc=xxxx,dc=xxxx"
        messageID: 4
        protocolOp: modifyRequest (6)
            modifyRequest
                object: uid=xxxx,cn=users,dc=ldap,dc=xxxx,dc=xxxx
                modification: 1 item
                    modification item
                        operation: replace (2)
                        modification userPassword
                            type: userPassword
                            vals: 1 item
                                AttributeValue: {SHA}fEqNCco3Yq9h5ZUglD3CZJT4lBs=

that fails with

Lightweight Directory Access Protocol
    LDAPMessage modifyResponse(24) constraintViolation (Password fails quality checking policy)
        messageID: 24
        protocolOp: modifyResponse (7)
            modifyResponse
                resultCode: constraintViolation (19)
                matchedDN: 
                errorMessage: Password fails quality checking policy

Server responds with an error, but pGina reports that the password is successfully changed.

Why pGina send encrypted password in AttributeValue? If I change userPassword with another software (JXplorer), AttributeValue field contains non-encrypted data and everything works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant