Open nmwael opened 3 years ago
further investigation tells med that it comes down to a conflict with spring boot keycloak adapters configuration key :"keycloak"
So both spring boot keycloak adapter and embedded keycloak relies on same configuration... in yaml, but totally different properties
There might be an workaround using something else than KeycloakSpringBootConfigResolver
further investigation tells med that it comes down to a conflict with spring boot keycloak adapters configuration key :"keycloak"
So both spring boot keycloak adapter and embedded keycloak relies on same configuration... in yaml, but totally different properties
im facing same problem how you solved it?
when I set these properties: keycloak: realm: xxxx auth-server-url: http://localhost:9999/auth ssl-required: none resource: xxxx-app public-client: true
Then embedded gets confused over missing properties: `APPLICATION FAILED TO START
Description:
Binding to target [Bindable@1842679 type = org.keycloak.adapters.springboot.KeycloakSpringBootProperties, value = 'provided', annotations = array[@org.springframework.boot.context.properties.ConfigurationProperties(ignoreInvalidFields=false, ignoreUnknownFields=false, prefix=keycloak, value=keycloak)]] failed:
` I suspect it because the configurations are the same, any pointers on what todo?