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.

Sign up for GitHub

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

Jump to bottom

Error 403 on Login #107

Closed
kamilczaja opened this issue Mar 15, 2024 · 2 comments · Fixed by #133
Closed

Error 403 on Login #107

kamilczaja opened this issue Mar 15, 2024 · 2 comments · Fixed by #133
Assignees
@kamilczaja
Labels
area/backend area/keycloak kind/bug Something isn't working. The software does not behave as expected or specified. status/updated MDS Authority Portal Issue was updated since last Bi-weekly
Milestone
R 22.03.

Comments

@kamilczaja
Copy link
Collaborator

kamilczaja commented Mar 15, 2024 •
edited
Loading

Description - What happened? *

Sometimes when trying to log in, error 403 appears. The error can be dismissed without problems by clicking "Sign in" on the error page.

Expected Behavior *

Error should not appear

Observed Behavior *

Error appears seemingly random

Steps to Reproduce

  1. Login by entering your email address and password
  2. Wait for a bit (I can't provide a specific timespan).
  3. Enter correct OTP.
  4. Error message will be displayed that the login attempt failed (probably because too much time has passed).
  5. You get redirected to the login screen.
  6. Enter your email address and password again.
  7. Enter correct OTP again.
  8. 403 error screen will be displayed.

Context Information

Working theory right now is that, once again, due to the login token expiring, the login fails and redirects back to the login page where the OAuth2-proxy tries to use the same nonce as before, resulting in an forbidden request.

Relevant log output

No response

Screenshots

Errorscreen_after_Login
@kamilczaja kamilczaja added status/blocked/needs-info requires more information in order to be completed kind/bug Something isn't working. The software does not behave as expected or specified. area/backend area/keycloak labels Mar 15, 2024
@kamilczaja kamilczaja added this to the Release March 22 milestone Mar 15, 2024
@jkbquabeck
Copy link
Collaborator

Current screenshot:
image

@jridderbusch jridderbusch self-assigned this Mar 18, 2024
@jridderbusch jridderbusch added status/updated MDS Authority Portal Issue was updated since last Bi-weekly and removed status/blocked/needs-info requires more information in order to be completed labels Mar 18, 2024
@jridderbusch jridderbusch removed their assignment Mar 19, 2024
@kamilczaja kamilczaja self-assigned this Mar 20, 2024
@kamilczaja

This comment was marked as outdated.

Sign in to view
@kamilczaja kamilczaja mentioned this issue Mar 20, 2024
Merged
@kamilczaja kamilczaja linked a pull request Mar 20, 2024 that will close this issue
Fix for error 403 #133
Merged
richardtreier added a commit that referenced this issue Nov 18, 2024
@richardtreier
fix: connector .env (2) (#107)
1486f89
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kamilczaja kamilczaja

Labels
area/backend area/keycloak kind/bug Something isn't working. The software does not behave as expected or specified. status/updated MDS Authority Portal Issue was updated since last Bi-weekly
Projects
None yet
Milestone
R 22.03.
Development

Successfully merging a pull request may close this issue.

Fix for error 403 sovity/authority-portal
3 participants
@jridderbusch @kamilczaja @jkbquabeck