Cloud discovery schedules get the creator as "Runs as", and it is not possible to change.

[Johannes]

When creating a "Cloud discovery", the schedules get the creator as "Runs as", and it seems like it is not possible to change this. Is this correct? Why on earth is it not possible to change it to a system user, so that the job does not fail if the person is inactivated?

[Fabian Kunzke]

Hello,

This behaviour is due to the schedules being "scheduled jobs" - similar to scheduled imports. Per default these always fill the Run As to match the created by if no other Run As is specified.

For discovery schedules this usually should not be an issue. If you want the Run As to be changed though, go into the schedule list view. Then add the "Run As" field to the list view. You should now be able to double-click onto that field and change the "Run As".

Hope this helps.

Regards

Fabian

[Johannes]

Hi Fabian,

There is no option to select any other "Run as" when creating the discovery job with the "Cloud Discovery" wizard.

Also, unlike for regular created discovery schedules, it is not possible to change the "Run as" value in the list view. It gives the error "Security prevents writing to this field", even when elevating role to "security_admin".

[Fabian Kunzke]

Hello,

sorry, i did not run into that issue beforehand. Are your schedules failing when you run them?

Regards

Fabian

[Johannes]

No schedules failing yet, but some of the schedules are created by external consultants, and I guess they might fail when they leave.

It should be possible (or even mandatory) to select a system user to run scheduled jobs during creation, but not even being able to change this afterwords without customizing with ACLs is a terrible design.