-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Add Authlib backend and test compatibility with Askar #14
Conversation
Signed-off-by: Daniel Bluhm <[email protected]>
Signed-off-by: Daniel Bluhm <[email protected]>
And add a failing test for further debugging Signed-off-by: Daniel Bluhm <[email protected]>
Signed-off-by: Daniel Bluhm <[email protected]>
Figured out what the issue was after much trial and tribulation: there were values that were b64 encoded and the ascii bytes of the encoded value were being used as part of the key derivation process instead of the decoded bytes. Specifically, |
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.
Aside from the broken import, I think this looks good overall
Signed-off-by: Daniel Bluhm <[email protected]>
Failing at the moment Signed-off-by: Daniel Bluhm <[email protected]>
Signed-off-by: Daniel Bluhm <[email protected]>
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.
LGTM
This PR adds an Authlib CryptoService backend.
To be perfectly frank, I'm not a fan of Authlib. For the functions we need from it, it is poorly documented and difficult to follow. My main goal in adding this backend is to (1) exercise the dependency inversion by having more than one backend around and (2) diagnose and debug compatibility issues we're seeing between this library and didcomm-python.