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.

Sign up for GitHub

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

Jump to bottom

Allow API clients to choose which key type to sign JWTs with #1

Closed
MicahParks opened this issue Apr 12, 2023 · 1 comment · Fixed by #5
Closed

Allow API clients to choose which key type to sign JWTs with #1

MicahParks opened this issue Apr 12, 2023 · 1 comment · Fixed by #5

Comments

@MicahParks
Copy link
Owner

Currently, JWTs are only signed with whatever the default key is in the database. Using the default configuration, this is the EdDSA key.

Add an option to all client requests to specify a signing key type for the JWT on a per-request basis. This supports the use case when a client application does not support the default key type.
@MicahParks
Copy link
Owner Author

Perhaps this should be the alg header value instead, as they kty is less specific.

@MicahParks MicahParks mentioned this issue May 27, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for client algorithm selection and database migrations MicahParks/magiclinksdev
1 participant
@MicahParks