Replies: 1 comment 1 reply
-
I saw those steps as requiring too much RP-specific logic to abstract when I rewrote the library to be stateless, "data in, decision out" methods. An RP would necessarily have to identify the user logging in and make sure the returned response And because the library is purely methods now, with no state, then that puts a burden on the RP to store authentication options to then cross-reference when a response is received, which is going to be implementation-specific. It didn't feel right to try and impose architectural decisions on RPs, as a library like py_webauthn, any more than WebAuthn already requires. That's been my thinking so far. |
Beta Was this translation helpful? Give feedback.
-
For example why are in the current verify_authentication_response.py the checks for 7.2. Verifying an Authentication Assertion step 4 and 5 missing. When I look back at older versions, like 0.47, of this library I see they checks are used, but not in the newer versions. Can somebody clarify this for me ? Thank you.
Beta Was this translation helpful? Give feedback.
All reactions