Re: Intended UAA-specific user identity fields in JWT access token ?
The access token used to double down as an identity token before OpenIDtoggle quoted messageShow quoted text
Connect was standardized, now that we have implemented id_token, we don't
really need it. but removing it would cause an backwards incompatible
On Thu, Mar 31, 2016 at 6:50 AM, Guillaume Berche <bercheg(a)gmail.com> wrote: