On 7/1/2014 9:42 AM, Stuart Douglas wrote:
There are many possible solutions:
> * Redesign domain-http
If by redesign you mean add some extension points to allow keycloak to
hook into it without requiring keycloak code in domain-http then this
is exactly what we should do.
If you want a hand with this I should be able to help you out.
Yes, that's pretty much what I was thinking. Thanks for the offer to
If there are no objections, I'll pursue the "redesign domain-http"
* By default, Keycloak is not available in core. But it could possibly
* Keycloak will be available in web-build and full build.
* Approximately 20 modules will be moved from full build to web-build.
* Delivery of Keycloak integration will be delayed. I don't know by how