You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for this library! I'm running into the following error when calling the verifyAuthenticationResponse function in the @simplewebauthn/server package, and was hoping I could get some help debugging. Here is the error and stack trace:
ERROR Error: Cannot get schema for 'ECDSASigValue2' target
at AsnSchemaStorage.get (/var/task/index.js:18997:17)
at AsnParser2.fromASN (/var/task/index.js:19247:50)
at AsnParser2.parse (/var/task/index.js:19237:26)
at unwrapEC2Signature (/var/task/index.js:33373:56)
at Object.verify (/var/task/index.js:33393:32)
at verifySignature (/var/task/index.js:33212:63)
at verifyAuthenticationResponse (/var/task/index.js:35174:21)
at async Object.verifyAuthResponse (/var/task/index.js:35735:28)
at async VerifyAuthOperation (/var/task/index.js:35784:10)
at async handle (/var/task/index.js:7366:22)
I'm thinking it's related to the allowed algorithms when generating the registration options, but I haven't been able to resolve it, trying both leaving the supportedAlgorithms field blank and explicitly providing supportedAlgorithmIDs: [-7, -257], when generating the registration options. Do you have any ideas as to what I'm missing here?
Reproduction Steps
I'm able to reproduce it with my local project, I can provide exact steps if needed. Its jsut going through the auth flow.
Expected behavior
I expect the verification to succeed, or at least fail with a different error, (invalid key, verification failed: invalid algorithm or something like that).
Below is the JSON object being passed into verifyAuthenticationResponse. I've masked a few of the fields, but let me know if they're needed to debug. I can also provide the options if needed
to my package.json (the top level one in a mono-repo), fixed the issue.
I'll leave this issue open for another day or so to increase the visibility, but my issue has been resolved!
Could you look into adding this gotcha to your docs somewhere (maybe a new troubleshooting section on the server page)? I'm sure other people will run into this issue at some point!
If you have to specify a resolution in your project, check that the version of asn1-schema is up to date with what's used by @simplewebauthn/server. If you still have to specify 2.0.8 then that sounds like a bug in the @peculiar series of libraries (since those libraries are well past 2.0.8) and I'll look into possibly logging a bug over there.
Describe the issue
Hi, thanks for this library! I'm running into the following error when calling the verifyAuthenticationResponse function in the
@simplewebauthn/server
package, and was hoping I could get some help debugging. Here is the error and stack trace:I'm thinking it's related to the allowed algorithms when generating the registration options, but I haven't been able to resolve it, trying both leaving the
supportedAlgorithms
field blank and explicitly providingsupportedAlgorithmIDs: [-7, -257],
when generating the registration options. Do you have any ideas as to what I'm missing here?Reproduction Steps
I'm able to reproduce it with my local project, I can provide exact steps if needed. Its jsut going through the auth flow.
Expected behavior
I expect the verification to succeed, or at least fail with a different error, (invalid key, verification failed: invalid algorithm or something like that).
Code Samples + WebAuthn Options and Responses
Relevant code snippet:
Below is the JSON object being passed into
verifyAuthenticationResponse
. I've masked a few of the fields, but let me know if they're needed to debug. I can also provide the options if neededDependencies
SimpleWebAuthn Libraries
Additional context
I've tested explicitly stating the supported algorithms as
supportedAlgorithmIDs: [-7, -257],
, leaving out [-8], but that leads to the same error.Let me know if I can provide any additional info to debug this error! Any help you could provide would be awesome, thanks!
The text was updated successfully, but these errors were encountered: