webMethods Integration Cloud and Cloud Deployment Documentation 6.0.0 | webMethods Integration Cloud | Settings | Access Control Lists
 
Access Control Lists
 
Adding or Updating Access Control Lists
You can use Access Control Lists (ACLs) to control the execution permission of an Integration. ACLs provide you with another level of control over who can execute specific Integrations. An ACL can be assigned to an Integration and a user can be associated with the ACL through the Access Profile. Therefore using ACLs, you can control the users who can execute an Integration.
Example 1
You have three users U1, U2, and U3. U1 is assigned to Access Profile AP1, U2 is assigned to Access Profile AP2, and U3 is assigned to Access Profile AP3. Each user has the Integration execution permission. There are also four Integrations IN1, IN2, IN3, and IN4 in your tenancy. Initially, U1, U2, and U3 can run all the four Integrations IN1, IN2, IN3, and IN4. Now you want IN1 to be executed only by U1 and not by U2 and U3. To do that, create an Access Control List, ACL1. Associate ACL1 to IN1. Then associate ACL1 to AP1. As U1 has already been assigned to AP1, IN1 can be executed by only U1. If you want IN1 to be executed also by U2, then associate ACL1 with AP2.
Integration Cloud provides you with a default ACL, Default, and this default ACL is associated with all Integrations. You can change the ACL associated with an Integration in the Integration Details page.
Example 2
You have three users U1, U2, and U3. U1 is assigned to Access Profile AP1, U2 is assigned to Access Profile AP2, and U3 is assigned to Access Profile AP3. Each user has the Integration execution permission. There are also four Integrations IN1, IN2, IN3, and IN4 in your tenancy. Initially, U1, U2, and U3 can run all the four Integrations IN1, IN2, IN3, and IN4. Now you want U1 to run only IN1 and not IN2, IN3, and IN4. To do that, create an Access Control List, ACL1. Associate ACL1 to IN1. Then associate ACL1 to AP1, AP2, and AP3. Now disassociate AP1 from the default ACL. As AP1 is associated with only ACL1, U1 will be able to execute only those Integrations associated with ACL1.
Users who have the Access Control permission under Settings  > Access Profiles > Administrative Permissions > User and Ownership Controls can edit the ACL information.
To edit an existing ACL other than the default ACL, select the ACL and click Edit. To delete an existing ACL other than the default ACL, select the ACL and click Delete. If you delete an ACL, the ACL will be removed from the associated Integration and the Integration will be associated with the default ACL. To create a new ACL, click Add New Access Control List.

Copyright © 2014- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.