I can indeed reproduce your problem but tbh I have no idea if this is an expected behaviour or not. And if it is a bug not sure if it's on the undertow or keycloak. Anyway could you open a ticket for this ? On Tue, Nov 22, 2016 at 9:14 AM, Filip Bielejec < filip_bielejec(a)trimble.com&gt; wrote: > Putting an webservice EJB annotated with WebContext changes the (already > configured) authorization method from KEYCLOAK to BASIC and effectively > locks the client out. > > I modified the keycloak product-demo example to demonstrate the problem: > > https://github.com/fbielejec/keycloak-demo > > Please note that the bean isn't called anywhere it is *just* on the > classpath. I'm not sure if this is the desired behaviour. > > Best, > fbielejec > _______________________________________________ > keycloak-user mailing list > keycloak-user(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-user >