When used with auth systems that create large keys (UAA) storing
sessions as cookies can cause the cookie to be larger than
browsers like. This somewhat awkwardly seperates id_token and
refresh_token out into their own cookies.
You could also switch out to filesystem or redis for session storage
but that adds more complication for runtime than this super simple use
case really warrants IMHO.
When used with auth systems that create large keys (UAA) storing sessions as cookies can cause the cookie to be larger than browsers like. This somewhat awkwardly seperates id_token and refresh_token out into their own cookies.
You could also switch out to filesystem or redis for session storage but that adds more complication for runtime than this super simple use case really warrants IMHO.
Signed-off-by: Paul Czarkowski username.taken@gmail.com