Description
There are times when a particular client may need to have additional data about the server instance/s where a KnoxToken can be used. For instance, it would be helpful to give a clue as to what cookie name may be expected by the KnoxSSO service.
After acquiring a token, a client may wrap the token in a cookie to be used by KnoxSSO compatible services/UIs.
I envision a single param with a comma separated list of KV pairs that would then be added as single elements to the JSON response and interrogated by the client before use of the token.