Jason Frey comments

Results 678 comments of


                                            Jason Frey

Cookie “miq_oidc_access_token” is invalid because its size is too big. Max size is 4096 B.

That's correct - that particular cookie isn't handled by our application at all, but instead by mod_auth_openidc for the /ui/service path. On the classic UI side you don't see the...

Cookie “miq_oidc_access_token” is invalid because its size is too big. Max size is 4096 B.

Actually I found it here: https://github.com/OpenIDC/mod_auth_openidc/blob/master/auth_openidc.conf#L539-L546 However, what's strange is it says if it's not set, it defaults to 4000 bytes per chunk, so based on that I don't understand...

Cookie “miq_oidc_access_token” is invalid because its size is too big. Max size is 4096 B.

Oh I see what you're saying - your theory is that since we call Set-Cookie explicitly, it's ignoring any cookie handling by mod_auth_openidc? If so, that would explain it.

Cookie “miq_oidc_access_token” is invalid because its size is too big. Max size is 4096 B.

cc @jrafanie @kbrock

Cookie “miq_oidc_access_token” is invalid because its size is too big. Max size is 4096 B.

@uejo You should be able to manipulate the conf file as you need on your appliance until you can get it working - if you can find a way to...

Cookie “miq_oidc_access_token” is invalid because its size is too big. Max size is 4096 B.

Can you verify that group switching still works as expected in the service UI and classic UI? (Group switcher is under the user icon in the upper-right, I believe)

Cookie “miq_oidc_access_token” is invalid because its size is too big. Max size is 4096 B.

@uejo This sounds like a great change to the documentation - can you make a PR in https://github.com/ManageIQ/manageiq-documentation/blob/master/auth/openid_connect.md ? Thank you!

Button role-based visibility rules do not work in UI Service

@GilbertCherrie Can you please take a look at this one?

Compiler: enable parallel codegen with MT

The RFC-2 link in the OP here points to a non-existing URL. Think it was supposed to be https://github.com/crystal-lang/rfcs/pull/2?

Blacklisted events are not user-configurable

So, IMO, this should 100% be in settings. We come out of the box with a list of default events in the settings, pluggable by provider, then the user can...