-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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 quarkus.webauthn.user-verification
default value is not working as expected
#38402
Labels
Comments
@StephenOTT Is it a duplicate of #38348 ? |
@sberyozkin i don't think so. |
Ah, either a code bug, or a doc bug. |
Indeed, the default is really |
FroMage
added a commit
to FroMage/quarkus
that referenced
this issue
Jan 26, 2024
FroMage
added a commit
to FroMage/quarkus
that referenced
this issue
Mar 12, 2024
FroMage
added a commit
to FroMage/quarkus
that referenced
this issue
Mar 19, 2024
franz1981
pushed a commit
to franz1981/quarkus
that referenced
this issue
Mar 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The web auth n config value:
quarkus.webauthn.user-verification
has a default ofrequired
https://quarkus.io/guides/security-webauthn#quarkus-security-webauthn_quarkus.webauthn.user-verification
https://github.com/quarkusio/quarkus/blob/main/extensions/security-webauthn/runtime/src/main/java/io/quarkus/security/webauthn/WebAuthnRunTimeConfig.java#L107
But when you DO NOT set the value / leave it as the default, the login process is returning:
"userVerification": "discouraged",
If you manually set the property in application.properties:
quarkus.webauthn.user-verification=required
then the userVerification property is properly set torequired
.Expected behavior
Default value is properly set
Actual behavior
Default value does not get set and value falls back to
discouraged
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: