Uploaded image for project: 'FORTRESS'
  1. FORTRESS
  2. FC-134

Don't initialize extended ldap controls with system properties

Attach filesAttach ScreenshotWatch issueCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0-RC40
    • 1.0.0-RC42
    • None

    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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            smckinney Shawn McKinney
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment