You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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...
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?
The text was updated successfully, but these errors were encountered: