Workload Automation 11.3.6 SP5 introduced a new EEM security policy type, as-sendevent.
It will check if a user has access to issue specific EVENTS via the sendevent command.
For more details see:
https://docops.ca.com/ca-wla-ae-wcc/11-4-2/en/release-information/ae-release-information/ae-release-11-3-6-sp5/new-features-11-3-6-sp5
We adjusted the as-sendevent policies such that user1 should have all actions and user2 would have some restrictions, such as no access to perform FORCE_STARTJOB or KILLJOB or the JOB_ON_HOLD event types. The EEM permission checker suggests we have configured this correctly as does autosec_test and running tests using the command line "sendevent". Yet from within WCC when user2 selects a job they see NO sendevent options available to them. Is there something we are missing?
In order to issue EVENTS against jobs from within WCC a user must have access within EEM's WCC policy ConfigurationControlEventDefault.
See:
EEM -> Application set to WCC0004 -> Manage Access Policies -> Access Policies -> ConfigurationControl -> ConfigurationControlEventDefault
Workload Automation 11.3.6 SP5 introduced a new EEM security policy type, as-sendevent.
It will check if a user has access to issue specific EVENTS via the sendevent command.
For more details see:
https://docops.ca.com/ca-wla-ae-wcc/11-4-2/en/release-information/ae-release-information/ae-release-11-3-6-sp5/new-features-11-3-6-sp5