Support base64url access for challenges; adjust legacy credential format #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reduces the need for RP servers to use internal methods by directly exposing the challenge as base64url, which is used by the (limited support) native formats as noted in #48 (a tool to produce the entire format will come as well!).
Additionally, this matches up the storage id formats for both credential formats, which as-is would not function as expected (new authorizations would return a v2, and subsequently could fail to find an existing matching v1 format depending on the lookup approach)
Warning
BC BREAK: this changes the storage identifier for the older credential format. This was noted in tests as a pre-1.0 possibility.
Fixes #59