Hi
AccessToken representations are flat. For example, the token
representation may have a token id, type, plus few additional
parameters, all being the siblings.
This requires using the specialized JSON providers in case when generic
structured token or error representations are used. For example, given
the following in Java:
public class AccessToken {
String key;
String type;
Map<String, String> additionalProperties;
}
it is difficult to use the generic JSON providers to correctly read a
sequence of name/value pairs into an instance of AccessToken.
It is not the major issue but I wonder would it be feasible to consider
introducing a simple container element for all the optional properties
which may be available in a given access token representation ? Probably
too late to consider but I'm sending the message just in case anyway
Cheers, Sergey
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
