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

Unable to login to report portal #298

Open
parasappafluke opened this issue Mar 7, 2023 · 1 comment
Open

Unable to login to report portal #298

parasappafluke opened this issue Mar 7, 2023 · 1 comment

Comments

@parasappafluke
Copy link

parasappafluke commented Mar 7, 2023

Hi,
I have installed report portal helm chart and it's dependencies, all the pods are in green. However i'm unable to login to the portal using default/1q2w3e credentials, getting 403 Forbidden error.
Where does default credentials store?

uat pod logs:
2023-03-07 07:35:25.603 DEBUG 1 --- [nio-9999-exec-6] o.s.security.web.FilterChainProxy : Securing POST /uat/sso/oauth/token 2023-03-07 07:35:25.604 DEBUG 1 --- [nio-9999-exec-6] s.s.w.c.SecurityContextPersistenceFilter : Set SecurityContextHolder to empty SecurityContext 2023-03-07 07:35:25.604 DEBUG 1 --- [nio-9999-exec-6] o.s.s.w.a.AnonymousAuthenticationFilter : Set SecurityContextHolder to anonymous SecurityContext 2023-03-07 07:35:25.605 DEBUG 1 --- [nio-9999-exec-6] o.s.s.w.a.i.FilterSecurityInterceptor : Failed to authorize filter invocation [POST /uat/sso/oauth/token] with attributes [authenticated] 2023-03-07 07:35:25.605 DEBUG 1 --- [nio-9999-exec-6] o.s.s.w.a.Http403ForbiddenEntryPoint : Pre-authenticated entry point called. Rejecting access 2023-03-07 07:35:25.605 DEBUG 1 --- [nio-9999-exec-6] s.s.w.c.SecurityContextPersistenceFilter : Cleared SecurityContextHolder to complete request 2023-03-07 07:35:25.606 DEBUG 1 --- [nio-9999-exec-6] o.s.security.web.FilterChainProxy : Securing POST /error

Note: I disabled minio since it was throwing exception in uat and service-api pods and pods were unable to start.

Versions:
Screenshot 2023-03-07 at 1 41 58 PM

Any help would be appreciated.

Thanks
Parasappa

@ci-operator
Copy link

Note: I disabled minio since it was throwing exception in uat and service-api pods and pods were unable to start.

To be clear, it sounds like you disabled Minio because (not it, but) the User AuThentication and API services were throwing exceptions, presumably from their failure to connect with Minio. Since the errors were likely from not accessing Minio, it doesn't make sense that removal of Minio would resolve this situation.

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

2 participants