Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] LDAP loader jobs can't find connection post 2.2 (vtldap) -> 2.3 (ldaptive) upgrade

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] LDAP loader jobs can't find connection post 2.2 (vtldap) -> 2.3 (ldaptive) upgrade

Chronological Thread 
  • From: Shilen Patel <>
  • To: Rob Gorrell <>, "" <>
  • Subject: Re: [grouper-users] LDAP loader jobs can't find connection post 2.2 (vtldap) -> 2.3 (ldaptive) upgrade
  • Date: Wed, 24 Jan 2018 20:27:39 +0000
  • Accept-language: en-US
  • Authentication-results:; spf=none
  • Ironport-phdr: 9a23:xtmt2xaqwELEyTLTDqG/sD//LSx+4OfEezUN459isYplN5qZrsWybnLW6fgltlLVR4KTs6sC17KP9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQpFiCagbb9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjm58axlVAHnhzsGNz4h8WHYlMpwjL5AoBm8oxBz2pPYbJ2JOPZ7eK7WYNEUSndbXstJVyJPHJ6yb5cBAeQCM+ZXrYfyp1oSohSxHgSjHv/jyjpSi3Pqx6A30eIsGhzG0gw6GNIOtWzZosj1NKcTVeC60q/IxijZYfxMxTfy9ozIeQ0mrPGXXbJwcM7RxlcpFw7ek1qQtI/lMC2P2usTrmeb8vNtWOSygGAprAFxpyKgxsYqioTRnoIV0FfE9SJ3wIYtIt24SUh7YcK+HJRMsCGaMpN6Qt4kQ250tyY20KMJtoOmfCQS1Zso2wfTZvKafIeU+B3jUf6RISpjhH58Zr6wmwu9/lS5xuDyS8a0zVBKoTZKktXVqHwCywHc5dSeRvZz40iuxyuA1x3V5+pZIk40jbLWJ4Mhz7IujJYev17PEjL1lUjylqOaaEsp9vaw5+j6YrjquIWQOoFuhgzwPakigMKyDfwmPgQTXmWX4+qx2KP58UHkQ7hGkuc6nrTbvZ3ZI8kQu7S3DBVP0ok57hayFzem38ocnXkANF9FfQiIj4ntO13XL/D5A+6zj0itnTtxwPDGP6HhDo/QIXjek7fuY6xx5FBBxwou1dxf5pRUBa8dIP/rR0P8tMLUAgU3PgCu3urqC9Fw2pkAVW+BHKOVKKbSvkWJ5uIrLemMfogVuDPlJvg+5/7ujHs5lkEbfaSywJQXdXO4Eep8L0qHfHXsn88NEX0WsQomUOzqlFqCXCZcZ3aoWKI8+yk7B5y8DYvaW4Ctm6KO3D2gHpBNYmBGC0uMEWvzd4maQfsMaSSSItN/nTweU7iuVZMh2Q+0uADk1rVnM7mcxipNj5XpnPdy/ffekRV6oSZrAMOHyWyJZ3xylWxOSjMriuQ360NnzUqb3LI9nudVD8d75vVVXx08OIKGieF2Fpq6Dg3becqRRUzjX86rGyoZT9QtzsUIblonXdiuk0aQ8TCtBuoul72PCZp8yqvA0ny5c919ynLL0oEtklorBMZDKDv11eZE6wHPCtuRwA2inKGwePFZhXaV+Q==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

The loader is actually still using vt-ldap.  We’re working on changing that soon.  But until then, if you’re using PSPNG, then you’ll be using/configuring both vt-ldap and ldaptive.


- Shilen


From: <> on behalf of Rob Gorrell <>
Date: Wednesday, January 24, 2018 at 1:54 PM
To: "" <>
Subject: [grouper-users] LDAP loader jobs can't find connection post 2.2 (vtldap) -> 2.3 (ldaptive) upgrade


We recently completed an upgrade to Grouper 2.3 and everything has gone quite well... we're back online with subject resolution to our ldap source, sql loading jobs, pspng conversion, etc... but one area we're currently struggling with is our all our LDAP loader jobs... which functioned normally prior to the upgrade, but now all complain:

"Cant find the ldap connection named: 'campusLdap' in the  Should have entry: ldap.campusLdap.url or ldap.campusLdap.configFileFromClasspath, Problem with ldap connection: campusLdap"

Prior to the upgrade, in Grouper 2.2, our looked like this:
ldap.campusLdap.url = "ldaps://,dc=uncg,dc=edu
ldap.campusLdap.user = someuser
ldap.campusLdap.pass = somepass

That syntax appeared to no longer work for us in Grouper 2.3. Working with converting from the PSP to PSPNG taught us that this needed to be reconfigured to account for the switch from vtldap to ldaptive. So in Grouper 2.3, our current now looks like this:

ldap.campusLdap.ldapUrl = ldaps://,dc=uncg,dc=edu
ldap.campusLdap.bindDn = somepass
ldap.campusLdap.bindCredential = someuser


But when we execute the job, the error message indicates it expects the old (vtldap) config of .url (not the new ldaptive syntax of .ldapUrl)... which is a bit confusing. So what is an LDAP loading source supposed to look like in under 2.3? All the wiki documention for loader and the error message being return would seem to indicate this hasn't changed from the past... but our own experience with PSPNG and knowledge of the switch to ldaptive would seem to hint otherwise.


Can anyone educate me on how ldap loading sources might need to be reconfigured post upgrade from 2.2 to 2.3?






Robert W. Gorrell
IT Manager, Identity and Access Management

University of NC at Greensboro

Archive powered by MHonArc 2.6.19.

Top of Page