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

Wrong text during enrolling email via multichallenge #3928

Closed
mont2fa opened this issue May 2, 2024 · 0 comments · Fixed by #3931
Closed

Wrong text during enrolling email via multichallenge #3928

mont2fa opened this issue May 2, 2024 · 0 comments · Fixed by #3931
Assignees
Labels
Topic: Policy in regards to event handler modules and events (can be function, DB or UI) Type: Bug Confirmed bug
Milestone

Comments

@mont2fa
Copy link

mont2fa commented May 2, 2024

if a user logins for the first time and doesn’t have any tokens yet instead of hard coded “Please enter your email address!”, header challenge text + footer challenge text are displayed (which should be displayed when asking for OTP)

@mont2fa mont2fa added the Type: Possible bug Suspected bug by user label May 2, 2024
@cornelinux cornelinux changed the title Enroll via multichallenge EMAIL (bug #2) Wrong text during enrolling email via multichallenge May 6, 2024
@cornelinux cornelinux added this to the 3.10 milestone May 6, 2024
@cornelinux cornelinux added Type: Bug Confirmed bug Topic: Policy in regards to event handler modules and events (can be function, DB or UI) and removed Type: Possible bug Suspected bug by user labels May 6, 2024
cornelinux added a commit that referenced this issue May 6, 2024
During mulitchallenge enrollment we should not use
the challengetext header and footer, since these are not
applicable.

Reordering the decorators solves this issue.

Closes #3928
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Topic: Policy in regards to event handler modules and events (can be function, DB or UI) Type: Bug Confirmed bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants