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