The behavior using 'json' differs from 'multi_json'

[Foxandxss]

Having in mind I just started with JWT a while ago, I see a difference between the two.

Back on node, I could save a simple integer as payload or even a string.

Here, I can do that also if I have multi_json but if not, it raises an exception so I am forced to save a hash.

It is not that important but it bugged me a while.

What do you think?

[yolk]

According to the current Draft the payload must (or even MUST!?) be an object:

JWTs represent a set of claims as a JSON object that is encoded in a
JWS and/or JWE structure. This JSON object is the JWT Claims Set. As
per Section 4 of RFC 7159 [RFC7159], the JSON object consists of zero
or more name/value pairs (or members), where the names are strings
and the values are arbitrary JSON values.

So I guess JSON is correct and MultiJSON/node are not. ruby-jwt should maybe even throw an exception on .encode in this case.