Automic Workload Automation

 View Only

  • 1.  Object authorization mass update

    Posted Oct 14, 2024 06:49 AM

    Hi all, 

    maybe someone can give me a hint how to mass update the object authorizations of our job/jobplan objects, besides editing every item manually.
    I've already checked the DB change documentation, but it seems this part of the job objects can't be modified by dbchange or I can't find it.

    In detail:

    • we have to remove the old users and user groups and replace it with the new user groups
    • we have to add the new user groups to jobs, which hadn't any authorization groups at all (these are few, we could for an DB change approach add a dummy group manually)

    Any recommendations how to do it via DB change or another feasible approach?

    Thanks in advance



  • 2.  RE: Object authorization mass update

    Posted Oct 14, 2024 06:57 AM

    Sry, I forgot to mark it as question instead of discussion, can a mod maybe change this?




  • 3.  RE: Object authorization mass update

    Broadcom Employee
    Posted Oct 15, 2024 02:47 AM

    Hi Tristan,

    if I understand your question correctly, then you are using the "Object authorization" tab of objects to assign users and user groups. Is there any specific reason for that? In general we recommend defining user groups and specify all the permissions within that user group. After that users can be assigned to those groups. Using the "Object authorization" tab should only be used in exceptional cases, for example if you would like to override user groups.

    Without understanding your use case in detail I would remove all the object authorizations  from all objects and replace them by permissions assigned via user groups.

    Regards, Markus




  • 4.  RE: Object authorization mass update

    Posted Oct 15, 2024 05:41 AM
    Edited by Tristan Lotz Oct 15, 2024 06:44 AM

    Hi, 

    we are currently having authorizations for user-groups and users and wanted to replace this by user-groups only.

    We are currently still figuring out what could be the best approach to this. Now that you pointed it out, your recommendation could make things easier, I will discuss this with my colleagues.

    Thank you very much for your input :)

    But still we would have the issue to remove the old user/user-groups from the objetcs - any ideas?