You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.
I need to know if there is a way to enable a debugger on the proxy and nexus itself, because even after following the instructions multiple times I still can't get it work, it seems the X-forwarded-user header is not being passed correctly and I end up not being able to log on nexus, I get these errors:
Checking the cookies I saw that 3 different JWT tokens are present in the cookie, not sure if this is the expected behavior:
The text was updated successfully, but these errors were encountered:
Hey @GMafra, I suggest you fork the nexus-proxy project in order to validate your assumptions. Then, maybe you'll find an issue and we can discuss it, maybe even contribute a fix. That would be awesome!
Quick question that might solve my problem: Are we required to create users on Nexus even if we have GCP authentication enabled?
From my understanding the Rut Auth capability automatically creates a local nexus user based on the authenticated user that is sent from IAP within the cookie, or is this not correct?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I need to know if there is a way to enable a debugger on the proxy and nexus itself, because even after following the instructions multiple times I still can't get it work, it seems the X-forwarded-user header is not being passed correctly and I end up not being able to log on nexus, I get these errors:
Checking the cookies I saw that 3 different JWT tokens are present in the cookie, not sure if this is the expected behavior:
The text was updated successfully, but these errors were encountered: