Hi Dmitry, Yes, that seems to be it. I am using Apache reverse proxy to get my Wildfly application on port 8080 accessible over port 443. My proxy rule was using localhost instead of myserver.example.com and after replacing localhost with actual hostname now it seems to be working. I say seems to be working because I now get past the localhost redirect issue, but it doesn't seem like the servlet container acknowledges I'm logged in. I am redirected back to the application with a parameter session_state=<long string of characters and numbers>. However, the EL expression on the return page: "${pageContext.request.userPrincipal eq null}" is showing true - suggesting that the Wildfly servlet container doesn't know I'm logged in. Does the Wildfly client adapter not integrate with container managed security? Thanks, Ryan ----- Original Message ----- From: "Dmitry Telegin" <dt(a)acutus.pro&gt; To: "Ryan Slominski" <ryans(a)jlab.org&gt;, "keycloak-user" <keycloak-user(a)lists.jboss.org&gt; Sent: Wednesday, August 8, 2018 7:23:54 PM Subject: Re: [keycloak-user] Wildfly Container Managed Security Constraint Redirect localhost Hi Ryan, Is your Wildfly (not Keycloak) behind a reverse proxy? Cheers, Dmitry Telegin CTO, Acutus s.r.o. Keycloak Consulting and Training Pod lipami street 339/52, 130 00 Prague 3, Czech Republic +42 (022) 888-30-71 E-mail: info(a)acutus.pro On Wed, 2018-08-08 at 16:34 -0400, Ryan Slominski wrote: