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

Array of additional tokens #39

Closed
PieterKas opened this issue Jul 4, 2024 · 2 comments
Closed

Array of additional tokens #39

PieterKas opened this issue Jul 4, 2024 · 2 comments
Assignees

Comments

@PieterKas
Copy link

Commenting as identity enthusiast as opposed to WIMSE co-chair.

The oth claim allows for a certain degree of extensibility, but raises a question about what to do if there is more than one additional token for which a hash should be included. should this be an array of hashes? How would an implementor know which of the tokens is corresponding to which of the hashes?

@bc-pi
Copy link
Collaborator

bc-pi commented Jul 11, 2024

The oth claim as it's defined in -00 is kinda garbage, if we're being honest.

Something more along the lines of what @yaronf suggested in #19 (comment) that resulted in #25 would probably be a better approach (to the extent we need this kind of extensibility anyway). While still aiming to avoid reinventing HTTP signatures...

@yaronf
Copy link
Collaborator

yaronf commented Oct 15, 2024

Decided to avoid, mainly due to complexity. See also #25.

@yaronf yaronf closed this as completed Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants