[FC-134] Don't initialize extended ldap controls with system properties

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0-RC40
• Fix Version/s: 1.0.0-RC42
• Assignee: Unassigned
• Reporter: Shawn McKinney
• Created: 07/Jan/16 21:27
• Updated: 06/May/16 15:22
• Resolved: 07/Jan/16 21:29

Description

Problem arose in an environment with another app that uses apache ldap api. The problem is fortress core initializes its extended ldap controls using system properties like this:
System.setProperty( StandaloneLdapApiService.EXTENDED_OPERATIONS_LIST, "org.openldap.accelerator.impl.createSession.RbacCreateSessionFactory,"
+ "org.openldap.accelerator.impl.checkAccess.RbacCheckAccessFactory,"
+ "org.openldap.accelerator.impl.addRole.RbacAddRoleFactory,"
+ "org.openldap.accelerator.impl.dropRole.RbacDropRoleFactory,"
+ "org.openldap.accelerator.impl.deleteSession.RbacDeleteSessionFactory,"
+ "org.openldap.accelerator.impl.sessionRoles.RbacSessionRolesFactory"
);

which classes with another program in same tomcat instance. When the 2nd program fires up ldap api, it tries to load the same extended ldap classes and gets a class not found exception.