Automic Workload Automation

 View Only

  • 1.  Login Object in the User Catalog is in Read-only mode

    Posted Mar 20, 2018 05:47 AM
    Hi all,

    I have moved a login object to a User Catalog and the User/Usergroup has been given all the access to the object, but still it is getting opened in Read-only mode. I want to let the user modify the login object,if required. Please tell me where did I go wrong.

    Regards,
    Srujan.




  • 2.  Login Object in the User Catalog is in Read-only mode

    Posted Mar 20, 2018 08:15 AM
    Hi.

    I am somewhat curious as to why you have a LOGIN object in a user catalog at all. I'm not saying it's wrong, but thus far I believed the User Catalog is useful for JOBS or JOBP or any "executable" objects. As LOGIN Objects are not "executable" but only a ressource to other jobs, I am not sure of their linking into the user catalog has ever been considered and/or properly tested.

    The usual way of letting users modify objects would NOT be User Catalog. User Catalog is for starting jobs (this may be your problem right there). The usual way would be to leave the LOGIN object in a folder and give the respective user (or group) modify permissions.

    Hth,
    Carsten


  • 3.  Login Object in the User Catalog is in Read-only mode

    Posted Mar 20, 2018 11:20 AM
    Hi Carsten_Schmitz_7883

    It's working fine now.The thing is like each user will have his own login object and whenever he runs the workflow, it will take the corresponding user's login object dynamically. And I want the user to update their domain password each time it expires so wanted to give them the write access. 

    Not sure how effective my idea is. :D

    Thanks,
    Srujan.


  • 4.  Login Object in the User Catalog is in Read-only mode

    Posted Mar 20, 2018 11:27 AM
    Hi Srujan,

    Great, thanks for letting us know :)

    Best,
    Carsten