More test vectors

[c2bo]

Fixes #216

I've moved the existing 2 bit examples and ascii art up - we can revert that change, but it felt more consistent to me that way
I am not exactly sure how to better displays the input (status values for specific positions) - any ideas?

Rendered version: https://drafts.oauth.net/draft-ietf-oauth-status-list/216-test-vectors/draft-ietf-oauth-status-list.html

[paulbastian]

I like it! I initially proposed to move the 2 bit acsii art up there, so that's fine for me :)
I think we require the CWT examples as well in the test vectors, having them for the same input values would be good.

[c2bo]

I like it! I initially proposed to move the 2 bit acsii art up there, so that's fine for me :) I think we require the CWT examples as well in the test vectors, having them for the same input values would be good.

Hmm, so we would provide the results in CBOR and JSON (we can easily re-use the same values)?

[paulbastian]

todo:

• status list token JWT rendering
• verifying test vectors inpendently wiht implementations

[paulbastian]

I've got the feedback that it may be irritating to not have dedicated 1-bit test vectors in the appendix

[c2bo]

I will create a longer 1 bit example then

[c2bo]

Todo: Wait for feedback on test vectors (check with at least one alternative implementation)

[markuskreusch-bdr]

I checked the test vectors by

• Defining the status[*] = * entries in the code (copy paste + search replace)
• Parsing the JSON and CBOR from the document with our library
• Checking in automated testcases, that all status entries have the expected value (0 for the ones not mentioned and the given value for the ones mentioned in the test vectors)

Verification was successful for all values.

Nevertheless I noticed, that the samples (CBOR and JSON) for the one bit status list have 2 instead of 1 bits.

[c2bo]

I checked the test vectors by

• Defining the status[*] = * entries in the code (copy paste + search replace)
• Parsing the JSON and CBOR from the document with our library
• Checking in automated testcases, that all status entries have the expected value (0 for the ones not mentioned and the given value for the ones mentioned in the test vectors)

Verification was successful for all values.

Nevertheless I noticed, that the samples (CBOR and JSON) for the one bit status list have 2 instead of 1 bits.

Thank you for catching that! That was a copy/paste mistake on my side and should be fixed now.
Could you re-check if everything looks fine now?

[markuskreusch-bdr]

Thank you for catching that! That was a copy/paste mistake on my side and should be fixed now. Could you re-check if everything looks fine now?

Everything is fine now.