Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UI] /users -> 401 Unauthorized -> Signed in successfully #3764

Open
shaburov opened this issue Mar 12, 2024 · 4 comments
Open

[UI] /users -> 401 Unauthorized -> Signed in successfully #3764

shaburov opened this issue Mar 12, 2024 · 4 comments

Comments

@shaburov
Copy link

image

@Pink-Bumblebee
Copy link

@shaburov , could you please share api-service log and your deployment information? (kuber or docker, db on same instance or separate. As much as possible without confidential data)

@shaburov
Copy link
Author

There are no more service logs left.
This is a bug about the UI, not about the backend. From the back 401, and on the UI - "Signed in successfully".

Copy link

That was the request from dev engineer.

@svaraksin-gd
Copy link

svaraksin-gd commented Mar 13, 2024

The same issue for me then I'm trying to land RP under base path. And probably that is why SSO doesn't work as well when using base path (RESOURCE_PATH from index).
API and UAT also was updated with an appropriate SERVER_SERVLET_CONTEXT_PATH value (with base_path).

Logs from API:
reportportal-new-api-866ffdcdb5.txt

There a couple of errors when you just openning UI login page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants