Is anybody using LDAP for accounts being used as owners within schedules on LINUX.
According to a case at BMC they mention:
=============================================
CONTROL-M/Agent doesn't officialy support LDAP, though it should work if the machine is properly configured like the customer's other machines.
The agent does use 'su' to run the job but from the brief description I saw it looks like the failure is earlier in the job's prerun checks.
Before the agent submits a job, it checks if the job owner exists and if it has execute permissions on the job script.
This is done using the getpwnam() system call. If the machine is configured properly, getpwnam() should check any user information database like /etc/passwd, NIS, ldap etc...
The agent is unaware of where the user is defined, it is up to getpwnam() to find it. It looks like the customer's machine has a
configuration problem preventing getpwnam() from getting the job owner's information from ldap.
We then demonstrated that the getpwnam() function is working succesfully by our own script.
Has anybody experience with this issue
