-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
nexus 3.15.2 does not allocate user accounts #32
Comments
Hi @mwmanley, what type of repository (maven, npm, ...) are you using within nexus? |
Primarily maven.
Tiny message typed on a tiny iPhone
… On Mar 15, 2019, at 10:05 AM, tobilarscheid ***@***.***> wrote:
Hi @mwmanley,
what type of repository (maven, npm, ...) are you using within nexus?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I am able to reproduce the stack trace with a fresh nexus 3.15.2 install. Login succeeds though, the user is assigned the correct roles and can interact with nexus. |
That's so weird. I'm literally consistently having the opposite experience. |
to clarify: I am running nexus 3.15.2 and all I tested is the web interface |
Yeah, same here. I can log in, which means that it's validating the token, but I get no roles associated with the GitHub team with which I am associating the role. |
What's more curious is that it doesn't work with new (post-upgrade) accounts. It's working for anyone that logged in pre-upgrade though. |
Groan. I was using the name that came from GitHub of @org/. I failed to notice that it was @org/ that GitHub was sending back, which the people that set up this group capitalized. So after switching to Team description, it worked. Sorry for the bother. I'm going to go scream into a pillow for a while since there were only two groups where these were mismatched, and they were both the ones that I was testing. |
Haha, glad you solved it. Still it would be great if we could get rid of that confusing stack trace... |
I got here by searching on the error message. I found it difficult to understand the solution. Eventually I found that the org/team role names need to exactly match what you see in the nexus3 log (although multiple org/team names will be combined into a single string until pr #43 is merged so you have to manually separate them until then.) |
Howdy,
We were forced to upgrade to nexus 3.15.2 due to the security issues with older versions. The newer version of nexus correctly looks up users in GitHub, but it no longer seems to allocate them internally. As a result, you get stack traces of user not found errors. I struck out user names and team names to comply with security:
I'll dig on my own to see if I can correct the issue, but I wanted to open this bug report to for others to see, maybe fix, the issue.
Thanks!
The text was updated successfully, but these errors were encountered: