fix: Atlassian Crowd authorization - #30898
Conversation
|
|
paulloft seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
thx helped |
|
Thanks alot, @paulloft . I built a patched release of the 6.4.5 tag with the two commits applied, then ran a test deployment. Worked perfectly. Fixed all errors, crowd login works and tested a bit the crowd administration page - synchronization / ping worked, too. Rolled the patched 6.4.5 release out for production, as I couldn't find any issues. :-) 👍 |
|
I'm not sure if the bug was introduced by this patch, but we found a very severe bug: If a user logins for the first time, the synchronization process overwrites erroneously an existing user with crowd data. E.g. user "alice.wonderland" logs in, user isn't found in the local RocketChat MongoDB database, then crowd user is fetched and a new account should be generated. Instead the whole account data of another user, like "bob.builder" is overwritten with the fetched crowd user data. Redacted logging output: If I'm not mistaken, the error should be somewhere in the |
|
Hi there, thanks for the contribution! 🚀 💯 Closing this PR because it's stale now and it was already fixed here: #31391 Questions? Help needed? Feature Requests?
|
Fixed broken Atlassian Crowd login after these changes
Issue(s)
Fixes #29285