LDAP with scheduled tasks
Posted: Mon Feb 17, 2014 12:20 pm
(InServ 3.1.2)
We are transitioning from local accounts to LDAP accounts on our 3PAR arrays for compliance reasons. We want to minimize any local account usage. If local accounts must be used, we would prefer they not be used for login to the array.
I notice that scheduled tasks like replication, AO and snapshots cannot be performed under LDAP accounts. Is there any way around this?
-Or-
Is there any way I can still have users login using their LDAP account to track administrative actions like creating/deleting volumes- but switch user (SU) or runas a local account to establish a scheduled task.
Any thoughts or experience around this would be appreciated
We are transitioning from local accounts to LDAP accounts on our 3PAR arrays for compliance reasons. We want to minimize any local account usage. If local accounts must be used, we would prefer they not be used for login to the array.
I notice that scheduled tasks like replication, AO and snapshots cannot be performed under LDAP accounts. Is there any way around this?
-Or-
Is there any way I can still have users login using their LDAP account to track administrative actions like creating/deleting volumes- but switch user (SU) or runas a local account to establish a scheduled task.
Any thoughts or experience around this would be appreciated