Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1369

Server-side caching mechanism support for OpenLDAP

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Extend server-side caching support to OpenLDAP.

            [CWD-1369] Server-side caching mechanism support for OpenLDAP

            Database-backed LDAP caching works for all directory types.

            David O'Flynn [Atlassian] added a comment - Database-backed LDAP caching works for all directory types.

            Greetings. I'm more than interested in caching feature added to OpenLDAP connector for Crowd. OpenLDAP will not ever support Persistent Search control, but it does support LDAP Content Synchronization Operation, which was accepted as RFC 4533. Is there a decision to implement this in the upcomming verstion?

            Stanislav Scherbakov added a comment - Greetings. I'm more than interested in caching feature added to OpenLDAP connector for Crowd. OpenLDAP will not ever support Persistent Search control, but it does support LDAP Content Synchronization Operation, which was accepted as RFC 4533. Is there a decision to implement this in the upcomming verstion?

            angel added a comment -

            David, Shihab Hi,

            Unfortunately, sync replication and persistent search are different mechanisms, and it appears that OpenLDAP doesn't expose the Persistent Search control. Although, since there are so many ways to configure OpenLDAP, it's possible that we simply haven't managed to set one of our test instances up to correctly expose it.

            From a quick review it seems that OpenLDAP does not come with the notion of persistent search, however I found a reference about a possible implementation based on syncrepl, here, Syncrepl client API.

            This is not only intended to provide replication capabilities, but also to implement client-side "persistent search"-like feature based on stock slapd (>= 2.3), without the need to revamp the persistent search IDs and code yet another overlay.

            Also a pertinent discussion found in http://www.openldap.org/its/index.cgi/Contrib?id=5612;expression=persistent

            Prob
            Cheers,
            A.

            angel added a comment - David, Shihab Hi, Unfortunately, sync replication and persistent search are different mechanisms, and it appears that OpenLDAP doesn't expose the Persistent Search control. Although, since there are so many ways to configure OpenLDAP, it's possible that we simply haven't managed to set one of our test instances up to correctly expose it. From a quick review it seems that OpenLDAP does not come with the notion of persistent search, however I found a reference about a possible implementation based on syncrepl, here, Syncrepl client API . This is not only intended to provide replication capabilities, but also to implement client-side "persistent search"-like feature based on stock slapd (>= 2.3), without the need to revamp the persistent search IDs and code yet another overlay. Also a pertinent discussion found in http://www.openldap.org/its/index.cgi/Contrib?id=5612;expression=persistent Prob Cheers, A.

            shihab added a comment -

            This will require implementing remote directory monitoring for OpenLDAP.

            Our preliminary investigations indicate that OpenLDAP 2.3.35 does not support the persistent search LDAP control. Attempting to execute a persistent search results in:

            javax.naming.OperationNotSupportedException: LDAP: error code 12 - critical extension is not recognized; remaining name 'o=sgi,c=us' 
            

            We will need to investigate RFC-4533 Content Synchronization Operation, which is supported by OpenLDAP.

            shihab added a comment - This will require implementing remote directory monitoring for OpenLDAP. Our preliminary investigations indicate that OpenLDAP 2.3.35 does not support the persistent search LDAP control. Attempting to execute a persistent search results in: javax.naming.OperationNotSupportedException: LDAP: error code 12 - critical extension is not recognized; remaining name 'o=sgi,c=us' We will need to investigate RFC-4533 Content Synchronization Operation , which is supported by OpenLDAP.

              Unassigned Unassigned
              38754ddc40c7 angel
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: