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

Restart authentication event type is not generated #29385

Closed
1 of 2 tasks
rmartinc opened this issue May 8, 2024 · 0 comments · Fixed by #29810
Closed
1 of 2 tasks

Restart authentication event type is not generated #29385

rmartinc opened this issue May 8, 2024 · 0 comments · Fixed by #29810
Assignees
Labels
area/authentication Indicates an issue on Authentication area backport/22.0 backport/24.0 kind/bug Categorizes a PR related to a bug priority/important Must be worked on very soon release/25.0.0 team/core-clients team/rh-iam
Milestone

Comments

@rmartinc
Copy link
Contributor

rmartinc commented May 8, 2024

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

authentication

Describe the bug

When a login performs a restart of the authentication process calling the restart endpoint:

http://localhost:8080/realms/otp/login-actions/restart?execution=e309dd92-423b-43d3-b5ae-08d7f6d9f455&client_id=account-console&tab_id=P4sW0009nm0

There is no success event generated for the restart.

Version

24.0.4

Regression

  • The issue is a regression

Expected behavior

A success restart event is registered.

Actual behavior

No event is registered.

How to Reproduce?

  1. Enable the realm user events: Realm settings -> Events -> User events settings -> Save events(On) -> Verify Restart authentication event type is saved.
  2. Enforce new users to configure OTP: Authentication -> Required actions -> Configure OTP -> Set as default action(set to On)
  3. Create a new user and set the credentials for the new user.
  4. Login to the out of the box account client using newly created user: http://localhost:8080/realms/otp/account/
  5. Enter user name and passwword for the newly created user when redirected to the login page: http://localhost:8080/realms/otp/protocol/openid-connect/auth?client_id=account-console&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2Frealms%2Fotp%2Faccount%2F%23%2F&state=9aea5066-bb85-45b6-86ec-46653b842e2b&response_mode=fragment&response_type=code&scope=openid&nonce=5cc80fd2-f911-4eb9-8aed-029b7504d758&code_challenge=bnC3C-uD4v1JZr8KLTAvfxkNsferlXoF_lZjrt5BXLk&code_challenge_method=S256
  6. The user is then redirected to the OTP page to provide their one time password: http://localhost:8080/realms/otp/login-actions/authenticate?execution=e309dd92-423b-43d3-b5ae-08d7f6d9f455&client_id=account-console&tab_id=P4sW0009nm0
  7. Modify the url by relacing "authenticate" with "restart" and then hit enter: http://localhost:8080/realms/otp/login-actions/restart?execution=e309dd92-423b-43d3-b5ae-08d7f6d9f455&client_id=account-console&tab_id=P4sW0009nm0
  8. This should redirect the user login page as expected. However, the event type Restart authentication is not generated in the realm user events even though the event type Restart authentication is available in the realm user events settings.

Anything else?

No response

@rmartinc rmartinc added kind/bug Categorizes a PR related to a bug status/triage labels May 8, 2024
@keycloak-github-bot keycloak-github-bot bot added area/authentication Indicates an issue on Authentication area team/core-clients labels May 8, 2024
@rmartinc rmartinc self-assigned this May 8, 2024
@rmartinc rmartinc added this to the 26.0.0 milestone May 8, 2024
@keycloak-github-bot keycloak-github-bot bot added priority/important Must be worked on very soon and removed priority/low labels May 8, 2024
rmartinc added a commit to rmartinc/keycloak that referenced this issue May 23, 2024
Closes keycloak#29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
mposolda pushed a commit that referenced this issue May 23, 2024
Closes #29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
rmartinc added a commit to rmartinc/keycloak that referenced this issue May 24, 2024
Closes keycloak#29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
(cherry picked from commit b258b45)
rmartinc added a commit to rmartinc/keycloak that referenced this issue May 24, 2024
Closes keycloak#29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
(cherry picked from commit b258b45)
rmartinc added a commit to rmartinc/keycloak that referenced this issue May 24, 2024
Closes keycloak#29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
(cherry picked from commit b258b45)
rmartinc added a commit to rmartinc/keycloak that referenced this issue May 24, 2024
Closes keycloak#29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
(cherry picked from commit b258b45)
rmartinc added a commit to rmartinc/keycloak that referenced this issue May 24, 2024
Closes keycloak#29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
(cherry picked from commit b258b45)
rmartinc added a commit to rmartinc/keycloak that referenced this issue May 24, 2024
Closes keycloak#29385

Signed-off-by: rmartinc <rmartinc@redhat.com>
(cherry picked from commit b258b45)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/authentication Indicates an issue on Authentication area backport/22.0 backport/24.0 kind/bug Categorizes a PR related to a bug priority/important Must be worked on very soon release/25.0.0 team/core-clients team/rh-iam
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant