-
Notifications
You must be signed in to change notification settings - Fork 2
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
Are examples realistic? #116
Comments
it's To present something more realistic, we could replace it with the JSON claims-set from EAT's intro, sign it with HS256 and have:
I'd like to minimise this kind of work at this stage. |
The b64 decoders I tried, two of them, don't decode 4c693475 to ... Encoding ... gives Li4uC I know it's a lot of work (and you have many docs to worry about!). I did all this work for EAT. If you don't do this, probably adding a note to indicate what they are so people don't try to interpret and get confused like I did. |
In the following, I don't think the example tokens are either real b64-encoded tokens or CBOR-encoded tokens. They probably should be to help people understand. For example, I don't know what 4c693475 is.
It would be a lot of work, but you could import EAT CDDL and use the .b64 and .cbor control operators to validate into them with the cddl tool. I did that with EAT and was able to make some useful corrections to my examples.
The text was updated successfully, but these errors were encountered: