Hi Lj Thanks for that advice - will try that and let you know if I manage to sort this out. Will also log a support ticket with BMC so long so that they can confirm on their side and log a bug if necessary.
Thanks again On Fri, Nov 8, 2013 at 5:28 PM, LJ LongWing <[email protected]> wrote: > ** > Brad, > One thing you may be experiencing is with the change from C LDAP plugin to > Java LDAP Plugin, one thing you could try is to disable the Java one, > re-implement the C one, and see if the problem goes away...if it does, > obviously log a bug on the Java version with BMC. If the problem remains, > you may have a mapping difference on your Vendor form, check what attribute > the Request ID field is mapped to on both systems to verify where the > problem may be coming from. > > > On Fri, Nov 8, 2013 at 6:27 AM, BradRemedy <[email protected]> wrote: > >> ** >> Howdy all >> >> Hope everyone is well >> >> We are in the process of testing a upgrade from 7.5 patch 003 to version >> 8 patch 002. On the old version of Remedy, we had a simple vendor form that >> connected to our AD server and returned the AD details of our users. >> >> On our test server, we have setup version 8 and configured the LDAP >> integration exactly the same way as our current live server. >> >> However, when we do a search on our live system (running 7.5 patch 003) >> on the vendor form, we get a result in the 'Request ID' field of 'johns'. >> >> The same searchon the version 8 system however, we are getting back >> "DC=abcops,DC=ne|t:-:johns" >> >> This is affecting our SSO solution and for the life of me I cannot figure >> out why we are getting a different format back. >> >> Has anyone experience this or have any idea on where I can start looking. >> >> I have also checked the source code in the AD system and >> the sAMAccountName is correctly stored as "johns". >> >> Any advice or assistance is appreciated. >> >> Thanks >> Brad >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
