1. OS (operating system) version (RHEL 5.8 32-bit) 2. Perl version (output from perl -v) (This is perl, v5.8.8 built for i386-linux-thread-multi) 3. ARSystem version you are connecting to (7.6.04) 4. API version you compiled against (764sp1) 5. ARSperl version (1.93)
Our 'User Base' as defined in the AREA LDAP Configuration form is CN=Users,DC=example, DC=com so it wasn't able to search through and find the account in OU=application, OU=Users,OU=EXAMPLE,DC=example,DC=com What we did as a workaround is created a local account within Remedy for this user and made its password match that of its AD counterpart. Do you know of another way around this? On Sun, Oct 5, 2014 at 8:19 AM, Tim Lank <[email protected]> wrote: > 1. OS (operating system) version (RHEL 5.8 32-bit) > 2. Perl version (output from perl -v) (This is perl, v5.8.8 built for > i386-linux-thread-multi) > 3. ARSystem version you are connecting to (7.6.04) > 4. API version you compiled against (764sp1) > 5. ARSperl version (1.93) > > > I can login to Microsoft sharepoint and other applications with the > appScript01 user listed below, so I know the Active Directory credentials > are correct. > > Is there something within the Remedy Admin interface that would > allow/disallow a login based on the location within the Active Directory > structure? > > Is it because it is in the following Active Directory OU?: > > CN=appScript01,OU=application,OU=Users,OU=EXAMPLE,DC=example,DC=com; > > Whereas, the rest of us users that are able to login are in the Users > container: > > CN=Smith\, William,CN=Users,DC=example,DC=com > > By policy, we are not allowed to put the appScript01 user directly in the > Users container. > > Is there a way to allow Remedy to accept its credentials also? > > Thanks in advance for your help. > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
