OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
Figure 31-1. ACL Program Interfaces
Application Code
DCE Library
ServerClient
DCE Library
ACL
Store
Application Code
code
Resolver Code
ACL
Library
Backing
Store
Library
Cell
Directory
Service
sec_acl_xxx()
code
generated
IDL
IDL
generated
31.1 The Client-Side API
The client-side API is a local interface consisting of a set of routines that are prefixed
sec_acl. This is the interface on which the default DCE ACL editor (the DCE control
program, or dcecp) is built. An application that needs to replace dcecp with a DCE ACL
editor or browser of its own calls this interface. The following subsections provide
specific information on the functionality that this API supports.
31.1.1 Binding to an ACL
Any operation performed on an ACL uses an ACL handle of type handle_t to identify
the target of the operation. The handle is bound to the server that manages the object
protected by the ACL, not to the ACL itself. Since an object may be protected by more
than one ACL manager type (see Chapter 24), the ACL itself can only be uniquely
31−2 Tandem Computers Incorporated 124245