Cloud Application Integration (On-Premises) : Service Development : Assigning and Managing Permissions for Elements : What Is an ACL?
What Is an ACL?
 
What Happens When a Client Runs a Service with ACLs?
Is ACL Usage Required?
Creating ACLs
ACLs and Inheritance
Default ACLs and Inheritance
An ACL controls access to packages, folders, and other elements (such as services, IS document types, and specifications) at the group level. An ACL identifies groups of users that are allowed to access an element (Allowed Groups) and/or groups that are not allowed to access an element (Denied Groups). When identifying Allowed Groups and Denied Groups, you select from groups that you have defined previously.
There are four different kinds of access: List, Read, Write, and Execute.
*List controls whether a user sees the existence of an element and its metadata; that is, its input and output, settings, and ACL permissions. The element will be displayed on screens in Designer and the Integration Server Administrator.
*Read controls whether a user can view the source code and metadata of an element.
*Write controls whether a user can update an element. This access also controls whether a user can lock, rename, or delete an element or assign an ACL to it.
*Execute controls whether a user can execute a service or a web service descriptor.
For more details about these types of access, see webMethods Integration Server Administrator’s Guide.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback