RocketChat / RocketChat/Rocket.Chat
ldap aliases not being followed
Open
@rodrigok is already working on this.
Since Feb 5, 2016.
area: authentication
type: bug
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
hi, we spent some considerable time in reversing on how the rocketchat code is behaving against ldap and we have the perception that it is not following alias objects... therefore it attempts to use the resolved dn of the alias object (instead of the provided aliasedObjectName) and failing in binding to ldap
we'll try to provide a fix, this was just for sharing with you the results of our investigation
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.