Mongo model is using just some helper reflection classes from
org.picketlink.common. It should be easy to fork some functionality and
completely remove dependency on org.picketlink.common from mongo model.
However picketlink is also used for Ldap integration and here it's more
So what exactly is the requirement for picketlink integration? Am I
understand correctly that all picketlink dependencies must be removed
from auth-server.war/WEB-INF/lib/ and added as deps to
If I understand correctly, this means that Keycloak must use same
Picketlink version, which is bundled with EAP. Do you know what is our
target EAP version and which version of Picketlink is in it?
Today I've upgraded Keycloak to newly released Picketlink 2.6.0.CR2,
which contains some nice LDAP improvements and fixes (like support for
RHDS and connection pooling). So it seems that I will need to revert
this and use some older picketlink version bundled in EAP instead:-(
On 29.4.2014 18:15, Bill Burke wrote:
Mongo model project seems to have picketlink dependencies:
These need to be isolated and removed as a dependency. Since we may be
introducing Keycloak into EAP (via Aerogear) we want to be sure we can
remove any version conflicting picketlink dependencies. So, anything
picketlink related has to be behind a plugglable and removable SPI.