We have a stash server (2.5) set up with a authentication directory from crowd. It is mostly working fine but in once case we have a user who is a member of various groups (stash-admin, stash-users, etc..) but when we look at those groups in the stash interface, she isn't there. But when we look at her user properties (admin/users/view), we see the expected groups listed in the groups TAB. This doesn't seem to be a problem for other users. Any idea what the cause could be?
Ok, after some more investigation, I see that I am getting some warnings in the log like this
2013-09-10 06:29:46,613 WARN [scheduler_Worker-7] c.a.c.d.DbCachingRemoteChangeOperations remote username [ trice ] casing differs from local username [ TRice ]. User details will be kept updated, but the username cannot be updated
Which means that at some point some of the usernames were capitalized, and then they were changed to lowercase in the crowd directory. It seems that every user that I have a warning like this about is also not showing up in their assigned groups. So the new question is, how do I fix this? How do I remove all of the local info about the user from Stash, and then re-sync the directory?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs