RocketChat / RocketChat/Rocket.Chat
[BUG] LDAP e-mails in viewed in comma seperated numbers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
E-mails are viewed in comma seperated numbers. I have for example 2 e-mails attached to my accounts, sync'ed from LDAP:
When I overwrite my e-mail to be readable, on the next background sync it just becomes numbers again. Seems to be stored in binary or so. LDAP is correct and shows the mails in plain text.
Server Setup Information:
- Version of Rocket.Chat Server: 0.61.2
- Operating System: Ubuntu 16.04 LTS
- Deployment Method(snap/docker/tar/etc): Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Disabled
- Node Version: v8.9.3
Steps to Reproduce:
- Sync LDAP user with Rocket.Chat
Expected behavior:
Syncs plain text email adresses.
Actual behavior:
Syncs binary or comma seperated list of numbers for email adresses.
Relevant logs:
[34mI20180221-00:08:41.194(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAP ➔ Connection.info Connecting ldaps://ipa.*:636
[34mI20180221-00:08:41.213(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAP ➔ Connection.info LDAP connected
[34mI20180221-00:08:41.215(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAP ➔ Bind.info Binding UserDN uid=*
[34mI20180221-00:08:41.219(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAP ➔ Search.info Searching user *
[34mI20180221-00:08:41.233(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAP ➔ Search.info Final Page
[34mI20180221-00:08:41.234(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAP ➔ Search.info Final Page
[34mI20180221-00:08:41.243(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAPSync ➔ info Import finished. Users imported: 6
[34mI20180221-00:08:41.244(0) rocketchat_logger rocketchat_logger.js:278 [34mLDAPSync ➔ info Import finished. Users imported: 6
Using FreeIPA as LDAP provider.
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.
Research direction
No source file or test is named. Start by reproducing the LDAP sync with the supplied FreeIPA setup and inspect the LDAPSync path and logs to compare the plain-text LDAP values with the stored user email addresses. Done means a background sync preserves readable email addresses rather than comma-separated numbers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100