[ https://issues.jboss.org/browse/TEIIDSB-34?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-34. --------------------------------- Fix Version/s: 1.0.3 Assignee: Ramesh Reddy Resolution: Done I could not use Keycloak Spring Boot adapter with JEE like web application, so I had to convert the OData service with following the Spring MVC using TEIIDSB-38. Then also the security context is not propagated to the application if you do not use the "Spring Security". Luckily Keycloak supports the Spring Security with additional code and configuration. So, I added another module called "keycloak-odata" that adds keycloak support on top of the regular OData service. In the end, doing this there were issues when "actuator" is also involved in the same project, so special steps needed to be taken to avert those and also expose some of the urls like $metadata, /actuator/health /swagger.json without the authentication. -- This message was sent by Atlassian Jira (v7.12.1#712002)