Hi
We are pretty new in the Angular and OpenID Connect land, so maybe we are doing things just plain wrong :)
Our IdentityServer (v3 btw) returns a "large" list of claims ("groupSids" and associated roles) from the UserInfoEndpoint
The jwt is about >5500 chars.
Now we wanted to implement a proper storage for the auth data, so that we can get the silent renew workflow working, but unfortunately the "authorizationDataIdToken" is too big for the cookie and the browser refuses to save it.
The library tries to load some important oidc-keys (e.g. "exp") from the JWT token so it seems the complete authorizationDataIdToken is needed.
Have you a suggestion for us? Are we using the userinfo endpoint wrong? We also could "split" the jwt in several cookies (like in the old ASP.NET days) and combine them during runtime, but I'm not sure if this is the way we should go.
Or just use the HTML5 localStorage?
We faced a similar problem with our WPF Windows client, but we were using Reference-AccessTokens and using access-tokens & refresh-tokens, but it seems in the Angular world it is different. In the fat client app I only store the accesstoken, the expire-date and the refresh-token and thats it. With them I can get a fresh accesstoken and do a proper logout without the super large JWT token.