-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fix oidc wrong success scenario #515
Labels
bug
Something isn't working
Comments
callmevladik
added a commit
that referenced
this issue
Dec 11, 2024
11 tasks
MykolaMarusenko
pushed a commit
that referenced
this issue
Dec 11, 2024
11 tasks
callmevladik
added a commit
that referenced
this issue
Dec 12, 2024
callmevladik
added a commit
that referenced
this issue
Dec 12, 2024
callmevladik
added a commit
that referenced
this issue
Dec 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There have been instances where users, upon passing an incorrect token while navigating in the portal, face errors related to resources access. This task aims to refine the user experience by ensuring that such errors are handled more gracefully. Instead of showing error messages related to resource access, the system should either prompt the user to check their authentication details or simply not display the inaccessible components without any error.
Acceptance Criteria
When an incorrect token is passed in the portal, the user should not see any error messages related to resource access.
The system should handle the scenario gracefully, possibly by not showing the components that require valid authentication, or by prompting the user to check their authentication details.
Ensure the solution does not affect the normal operation of the portal when a correct token is used.
The text was updated successfully, but these errors were encountered: