[
https://issues.apache.org/jira/browse/FC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-134.
-------------------------------
Resolution: Fixed
initialize instead like this:
List<String> listExOps = new ArrayList<>();
listExOps.add(
"org.openldap.accelerator.impl.createSession.RbacCreateSessionFactory" );
listExOps.add(
"org.openldap.accelerator.impl.checkAccess.RbacCheckAccessFactory" );
listExOps.add(
"org.openldap.accelerator.impl.addRole.RbacAddRoleFactory" );
listExOps.add(
"org.openldap.accelerator.impl.dropRole.RbacDropRoleFactory" );
listExOps.add(
"org.openldap.accelerator.impl.deleteSession.RbacDeleteSessionFactory" );
listExOps.add(
"org.openldap.accelerator.impl.sessionRoles.RbacSessionRolesFactory" );
LdapApiService ldapApiService = new StandaloneLdapApiService( new
ArrayList<String>(), listExOps );
> Don't initialize extended ldap controls with system properties
> --------------------------------------------------------------
>
> Key: FC-134
> URL: https://issues.apache.org/jira/browse/FC-134
> Project: FORTRESS
> Issue Type: Bug
> Affects Versions: 1.0.0-RC40
> Reporter: Shawn McKinney
> Fix For: 1.0.0-RC41
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
