Automic Workload Automation

Expand all | Collapse all

user access to single workflow

Shravani Vedantham

Shravani VedanthamJun 14, 2018 01:47 PM

  • 1.  user access to single workflow

    Posted Apr 18, 2018 02:33 AM

    Hello All, 

    I need to create a new user who will be able to trigger a single worklfow. Is it possible to assign privileges to account to allow trigger only a single workflow or at least allow access to single directly ? 

     

    Can You help me on this ? 

     

    Regards, Krystian



  • 2.  Re: user access to single workflow

    Broadcom Employee
    Posted Apr 19, 2018 08:31 AM

    Hi,

    Can you tell us the scheduler or manager you are referring to?

    Is this dSeries or AutoSys?

     

    Thank you,

    Nitin Pande

    CA Technologies



  • 3.  Re: user access to single workflow

    Posted Apr 19, 2018 09:36 AM

    hi, Sorry. I'm not sure what dSeries or AutoSys means. My question is related to the Automic UC4 scheduler tool. 

     

    Regards, Krystian



  • 4.  Re: user access to single workflow

    Posted Apr 19, 2018 09:25 AM

    If your question is concerning CAWA DE scheduler, and so by the 'workflows' you meant the DE events, then there are two permission types - the EVENT and the EVENTX, which could be set for either all events or a group of events by using wild characters, and for a particular event by specifying its literal name.

    These permissions, being assigned to either a user and/or a group, would regulate the events triggering.



  • 5.  Re: user access to single workflow

    Posted Apr 23, 2018 03:16 AM

    Hi Krystian,

     

    do you currently use a permission system ?

     

    If not you can put all executable objects on the NOT list and only the one JOBF to the allow list.

    and you should specify the Workflow as allowed.

     

    cheers, Wolfgang



  • 6.  Re: user access to single workflow

    Posted Apr 23, 2018 06:37 AM

    Two small remarks to the fine answer by Wolfgang:

     

    • "not" permissions still (afaik) have issues in Automic V12, so I would avoid them. But since the default is "no permissions", if you have a user that has permissions only to the explicitly named things he shall execute (i.e. that workflow and the included items, see below), then this achives the same thing.
    • Again afaik, the user needs execute permissions to the workflow AND the included objects. So you have to make multiple rules and give execute rights to the explicitly and unambigously named workflow, plus the contained objects.

     

    Hth,



  • 7.  Re: user access to single workflow

    Posted Apr 27, 2018 12:27 AM

    Hi Wolfgang, Thanks for Your response. 

    I'm not sure if our environment is setup to permission system. How can I detect this ? Can You advise ? 

    Until now I can edit dedicated user account and see the following tabs (Header, User, Authorizations, Privileges, UserGroups and Documentation). We are having a few groups that users are assigned with different privileges. I don't see the options here from User perspective or Group perspective that I can assign someone to have ability to modifiy only a single workflow. 

    Can You give more info how to achieve this ? 

     

    Regards, Krystian



  • 8.  Re: user access to single workflow

    Posted Apr 27, 2018 03:46 AM

    I'm not sure if our environment is setup to permission system. How can I detect this ? Can You advise ?

    I believe what Wolfgang was saying is not so much "do you have the permission system on or off", but "do you make structured use of the existing permission system at this time"

     

    You can, afaik, not not use use the permission system in the Automic AE/UC4 server in terms of totally disabling it, and there are no alternative mechanisms that would replace the permission system. You can, however, chose to not use fine grained permissions and give everyone permissions to everything in the existing permission system. It's not wise, but one could.

     

    In so far I believe Wolfgang was asking whether you're already in a good position to use the permission system as a means to solving your issue, by having a fine-grained permission structure in place.

     

    None of this changes the nature of the answer though, it'll just be more or less effort to implement depending on how your current setup of the permissions within the permission system are arranged.

     

     

    Hth.



  • 9.  Re: user access to single workflow

    Posted Apr 27, 2018 04:12 AM

    Hi

     

    Thanks, Carsten, you know what I mean :-)

     

    Sorry for being to fuzzy in my answer....

     

    Yeah if you do not make use of permissions and naming concept at the moment its a bit tricky but should be no problem.

    A good start is reding the documentation starting here: Automic 

     

    The most basics: you must assign rights for the folder and the objects in it seperately

    NOT overrrules all others

    you must assign rights for all contained objects of the workflow

     

    I would suggest creating a test Workflow with 2 testjobs and playing a bit with the credentials with a test user.

     

    Plan B: If yo user should only be able to start one dedicated workflow, you could install a CALL API (WIN ode Linux) that starts this workflow. Using this method the user does not need to login to AWI or JAVAui but simply doubeclicks on an icon on his (WIN) desktop.

     

    cheers, Wolfgang



  • 10.  Re: user access to single workflow

    Posted May 29, 2018 05:37 AM

    hi Wolfgang, 

    I tried setup access to single workflow but it is a quite complex. I haven't achieved a good solution for this.

     

    I'd like to create a CALL API for Windows to user to double click on icon on his desktop. Can You give more info how to achieve this ? 

     

    Regards, Krystian



  • 11.  Re: user access to single workflow

    Posted May 29, 2018 10:53 AM

    I have one customer that can log on and can only execute a single job.  To do this with the user security system I did the following;

    1. Attached the user to the USER_GROUP that provides read-only access to the system.

    2. Also attached the user to the USER_GROUP that provides submit rights to the desired workflow.

     

    Setting up the second user group was a trial-and-error process for me. It wound up needing these 5 grants;

    1. HOSTG <name> - to authorize him to run things on the desired agent group.

    2. JOBI "*' - to authorize him to execute includes

    3. JOBS <name> - to authorize him to execute the job in question

    4. PRPT <name> - to authorize him to execute the attached promptsets

    5. QUEUE <name> - to authorize him to run objects in the target queue



  • 12.  Re: user access to single workflow

    Posted Jun 14, 2018 12:42 PM

    Hi Pete

     

    Could you please send me screenshots of how you setup the security, if its feasible. I am trying to achieve this for a workflow which has multiple workflows and jobs in it . Very much appreciated.

     

    Thanks

    Shravani



  • 13.  Re: user access to single workflow

    Posted Jun 14, 2018 01:41 PM

    This is the custom set of grants I spoke of.  I've never done this for a workflow, only for this one job called "CLEARDBCACHE" that I needed to allow our DBA staff to execute;

     

    CustomUserGroup



  • 14.  Re: user access to single workflow

    Posted Jun 14, 2018 01:42 PM

    Even if you don't use any includes (JOBI) in your scripts, I believe you still need a JOBI grant because Automic executes client-0000 includes as part of its framework processes.



  • 15.  Re: user access to single workflow

    Posted Jun 14, 2018 01:47 PM

    Thank you so much!. I will test by changing my settings.