Skip to content
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

Move Jwt functionality from credentials package to dids or crypto package #794

Open
shamilovtim opened this issue Jul 26, 2024 · 0 comments
Assignees
Milestone

Comments

@shamilovtim
Copy link
Contributor

  1. Currently the Jwt functionality lives in the credentials package. This requires installing the credentials just to use Jwt creation, signing or verification. To fix we should move Jwt to the DIDs package.

  2. Jwt has a hard dependency on BearerDid which is an abstraction from the DIDs. If we wanted Jwt to live in the crypto package (rather than the DIDs package) then we must remove Jwt's hard dependency on BearerDid. This probably means passing in the signer separately as a parameter to Jwt functions.

@shamilovtim shamilovtim changed the title Move Jwt functionality from credentials package to crypto package Move Jwt functionality from credentials package to dids or crypto package Jul 26, 2024
@shamilovtim shamilovtim self-assigned this Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Up Next
Development

No branches or pull requests

1 participant