Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.2.0
    • Component/s: LDAP

      Description

      Looking at the calls that are going on when the scopes are checked it looks like it gets a list of scopes within hpccinternal, and then for each of those calls ldap again to see if there any rights for child scopes:

       

      CLdapClient::getResources() at ldapconnection.cpp:3,467 0x7fa392feec3c CLdapClient::getResources() at ldapconnection.cpp:3,467 0x7fa392feec3c CLdapClient::getResources() at ldapconnection.cpp:3,462 0x7fa392feeb76 CLdapClient::getResourcesEx() at ldapconnection.cpp:3,542 0x7fa392fef411 CLdapClient::getManagedFileScopes() at ldapconnection.cpp:6,118 0x7fa392ffd625
      
      

       

      this CLdapClient * const 0x46847d0 this CLdapClient * const 0x46847d0
      ld LDAP * 0x7fa364004350
      rtype SecResourceType RT_FILE_SCOPE
      basedn const char * 0x7fa3640641b0 "ou=astarr,ou=hpccinternal,ou=files,ou=dataland_ecl,dc=internal,dc=sds"
      prefix const char * 0x7fa364064180 "hpccinternal::astarr::" resources IArrayOf<ISecResource> & {...} attribute char * 0x0 message LDAPMessage * 0x0 basednbuf StringBuffer {...} 

      So each internal ldap scope causes another request to ldap to find child scope information.  That is painful, particularly over a transatlantic VPN!

       

       

       

        Attachments

          Activity

            People

            • Assignee:
              russwhitehead Russ Whitehead
              Reporter:
              ghalliday Gavin Halliday
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: