Hi, This may be a non starter for Sling, but I am seeing a need to reuse the pattern used by the PluggableLoginModule and the PluggableDefaultAccessManager.
I need to re-use that pattern on the PrincipalManager and the UserManager so that I can associate a Sling instance with externally held user objects and not have to push all the user information into Slings internal UserManager. At the moment this is just at the planning stage, and I havent written any code, but it would mean replacing the standard DefaultSecurityManager that comes with Sling with a modified one (PluggableDefaultSecurityManager) that instances PluggablePrincipalManager(s) and PluggableUserManager(s). Firstly: WDYT? Secondly: Can you see any problems ? If this is not for Sling, its not a blocker for me as I have customised server bundle already with modifications to the ACLProvider and patches to group permissions. There is documentation in progress at [1], scroll to the bottom of the page where the relevant part is. Ian 1 http://confluence.sakaiproject.org/display/KERNDOC/KERN-504+Groups+Pull+Integration
