-
Notifications
You must be signed in to change notification settings - Fork 61
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
Allow to pass expected origin to verify #365
Conversation
expect(public_key_credential.client_extension_outputs) | ||
.to eq({ "txAuthSimple" => "Could you please verify yourself?" }) | ||
expect( | ||
public_key_credential.client_extension_outputs | ||
).to eq({ "txAuthSimple" => "Could you please verify yourself?" }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only code style fixes.
expect(public_key_credential.authenticator_extension_outputs) | ||
.to eq({ "txAuthSimple" => "Could you please verify yourself?" }) | ||
expect( | ||
public_key_credential.authenticator_extension_outputs | ||
).to eq({ "txAuthSimple" => "Could you please verify yourself?" }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only code style fixes.
Hi @brauliomartinezlm, thanks for your feedback. I have seen that #368 was merged, which is great. There is no v3 alpha2 tag yet, but I assume it's the same as master at the moment, right? I will give it a try, thanks for your support 👍🏼 |
Closed in favour of using v3 of this gem. |
@manubo I've just released 3.0.0.alpha2. Hope it worked as you needed. |
Yes, works like a charm, thanks @brauliomartinezlm 👍🏼 |
Both
WebAuthn::AuthenticatorAttestationResponse#verify
andWebAuthn::AuthenticatorAssertionResponse#verify
accept the parameter
expected_origin
, but the calling methodsPublicKeyCredentialWithAttestation#verify
andPublicKeyCredentialWithAssertion#verify
,respectively, do not.
We have a multi-tenant system where each tenant has its own subdomain and need to be able to pass the origin when validating the data.