Are there any API changes after v0.5.0? #135
-
|
Hello! I'm from the Casdoor community. We recently encountered an issue when using Webauthn, and the detailed description is here. We have temporarily solved the bug by rolling back Webauthn in go.mod to v0.5.0, but we still need to find out what caused this issue to use the latest version of Webauthn. I would like to ask if there are any API changes after v0.5.0, especially between v0.5.0 and v0.6.0. In addition, based on my personal attempts, it seems that the issue occurred since this commit . I would greatly appreciate any feedback you can provide on this matter. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Per the release notes (and linked issue PR etc) there was a fix to one of the structs which previously was not using the specific Marshaller interface (ghosted). The specifics of the change (specifically with the challenge) are that if you're using the Base64 Standard encoding/decoding that it will fail, you need to ensure you're using the Base64 URL encoding (unpadded). |
Beta Was this translation helpful? Give feedback.
-
|
Side note, this brings the library to parity with the specification and the upcoming .toJSON() methods. I'd also recommend @simplewebauthn/browser. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your suggestion, I will look into it |
Beta Was this translation helpful? Give feedback.
-
|
No worries! Let me know if you have other questions/suggestions, now or in the future. |
Beta Was this translation helpful? Give feedback.
Per the release notes (and linked issue PR etc) there was a fix to one of the structs which previously was not using the specific Marshaller interface (ghosted). The specifics of the change (specifically with the challenge) are that if you're using the Base64 Standard encoding/decoding that it will fail, you need to ensure you're using the Base64 URL encoding (unpadded).