Tero Saarni

I think this would rather be a request for Envoy as also the existing `X-forwarded-*` logic is implemented there. With a quick glance at the proposed NGINX approach, it seems...

I'm cc'ing @qinqon, @cbandy, @kaovilai in case you are interested to comment this PR as well.

/assign @vincepri

Hi @vincepri, If you have a moment, could you please take a look? Your feedback would be greatly appreciated 🙏

The `redirectURL` is the website to be protected. Also `redirectPath` must be set to some non-existing path within the website, it will be intercepted by contour-authserver when Keycloak redirects back...

@hsimon-hashicorp @stevendpclark :wave: Just a gentle nudge :smile: I just wanted to follow up on this PR and check if you had a chance to consider its inclusion, as it...

Thanks @pedroigor! > If I got it correctly, we are going to have multiple identifiers so that we can use key|trust stores for different purposes: LDAP client, SMTP, HTTP Client,...

@pedroigor I was also thinking a bit about realm specific trust|key store problem when responding to https://github.com/keycloak/keycloak/issues/13300#issuecomment-1239850056. In a way there is discrepancy in component configuration when it comes to...

Thank you @pedroigor. > As I mentioned before, it should be fine for now to support server-level keystores. If we agree that the current proposal is OK even though realms...

@pedroigor and @mposolda May I ask for your help, it would be great if we could proceed with this feature! @mposolda from your comment https://github.com/keycloak/keycloak/pull/7365#issuecomment-1293440648 I understand that you prefer...