-
Notifications
You must be signed in to change notification settings - Fork 41
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
Simplify the <issuer>/raw/jwt/sign example #386
Comments
This issue has been marked as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The endpoint
/raw/jwt/sign
requires 2 parameterswalt-key
andwalt-subjectDid
If passed incorrectly, the endpoint returns unexplained messages, such as:
If we were follow our intuition, we would use the
/wallet-api/wallet/{wallet}/keys/generate
and/wallet-api/wallet/{wallet}/dids/create/key
endpoints to get the missing data.However, two things make life difficult for the developer here:
The key generation endpoint, for example, returns in such a format that is not accepted out of the box by the
walt-key
parameter.If the user manage to generate the key in the expected JWK format (e.g. XXXXXX), he tends to use the key in its raw form in the
walt-key
field instead of wrapping it as{"type":"local","jwk":"XXXX"}
How can we make this endpoint testing experience more intuitive and less laborious?
The text was updated successfully, but these errors were encountered: