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

WebAuthn Flows Broken in login.v2 #32578

Closed
2 tasks done
ThoreKr opened this issue Sep 2, 2024 · 3 comments
Closed
2 tasks done

WebAuthn Flows Broken in login.v2 #32578

ThoreKr opened this issue Sep 2, 2024 · 3 comments

Comments

@ThoreKr
Copy link
Contributor

ThoreKr commented Sep 2, 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

login/ui

Describe the bug

As a follow-up to #32365, this issue also affects the login.v2 theme making it impossible to login using a security or registering a new one. The error in the js console is the same

TypeError: Failed to resolve module specifier "rfc4648". Relative references must start with either "/", "./", or "../".

Version

25.0.4

Regression

  • The issue is a regression

Expected behavior

Login with a security key or registration of a new one is possible.

Actual behavior

The error mentioned above is thrown.

How to Reproduce?

Have a keycloak instance with the login2 feature flag enabled.
Enable it in a realm and create a webauthn enabled browser flow.
Try to register a new key.

Anything else?

It used to work in 24.0.x

@keycloak-github-bot
Copy link

Due to the amount of issues reported by the community we are not able to prioritise resolving this issue at the moment.

If you are affected by this issue, upvote it by adding a 👍 to the description. We would also welcome a contribution to fix the issue.

jonkoops added a commit to jonkoops/keycloak that referenced this issue Sep 2, 2024
Closes keycloak#32578

Signed-off-by: Jon Koops <jonkoops@gmail.com>
@jonkoops
Copy link
Contributor

jonkoops commented Sep 2, 2024

Fix for this is up under #32589

ahus1 pushed a commit that referenced this issue Sep 10, 2024
Closes #32578

Signed-off-by: Jon Koops <jonkoops@gmail.com>
@ahus1
Copy link
Contributor

ahus1 commented Sep 10, 2024

Closing as this has now been merged in the release 25 branch.

@ahus1 ahus1 closed this as completed Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants