Hannes,
The main issue here is that JWT has been built to be used for things
other than OAuth tokens (assertions, for instance), and that the
introspection endpoint is very specifically tied to OAuth. At Torsten's
suggestion, I've tried to align the output of the introspection endpoint
to the
Hi Mike, Hi Justin,
when I looked at the JWT and the draft-richer-oauth-introspection documents I
noticed that the two are not aligned (neither from the fields that are
supported nor from the way how the fields are defined).
IMHO draft-richer-oauth-introspection must not define new elements
