Hi to all.
I have a doubt.
The specified users in Control-M/Server Security, what functionality they have.
What differences exist between these users/groups and users of authentication.
I would appreciate the answers.
Thanks very much to all.
Control-M/Server Security.
To enforce the server security you must switch it on via Option 5 in the "CONTROL-M System Parameters" panel.
In general these settings should be the same as on the Enterprise Manager, the reason you have places to do what is essentially the same task is that the products were developed seperately.
Now you can do them as Groups it makes life a lot easier, but some sites still don't bother with switching this option on.
In general these settings should be the same as on the Enterprise Manager, the reason you have places to do what is essentially the same task is that the products were developed seperately.
Now you can do them as Groups it makes life a lot easier, but some sites still don't bother with switching this option on.
Hi,
If you have full security set to NO, Control/M check only users/groups in Control/M EM system (During NDP and when ordering jobs).
If you set full security to YES, you must also configure security on the Control/M Server side. You must configure scheduling table security and job security.
You can use option 5 or the ctmsec utility. From Control/M v. 7 you can also use Coinfiguration Manager.
I have full security set to yes in one customer environment because they want to secure the job execution. Only the ctm admnistrator can change Control/M Server security and in the ajf authorization he authorize unix local users to execute job (the job owner).
For example we define the possibility to user jdoe to execute jobs on server srv1.
The problem is the increasing of configuration and you must be very attentive to set table security because is very easy to don't order table during NDP configuration errors.
Regards,
Fabrizio
If you have full security set to NO, Control/M check only users/groups in Control/M EM system (During NDP and when ordering jobs).
If you set full security to YES, you must also configure security on the Control/M Server side. You must configure scheduling table security and job security.
You can use option 5 or the ctmsec utility. From Control/M v. 7 you can also use Coinfiguration Manager.
I have full security set to yes in one customer environment because they want to secure the job execution. Only the ctm admnistrator can change Control/M Server security and in the ajf authorization he authorize unix local users to execute job (the job owner).
For example we define the possibility to user jdoe to execute jobs on server srv1.
The problem is the increasing of configuration and you must be very attentive to set table security because is very easy to don't order table during NDP configuration errors.
Regards,
Fabrizio