Remote Automation: Security

|  Overview |  How Do I |  Sample

Remote Automation supports a basic level of security to allow a server application writer (or, rather, its administrator) to specify how a specific object may be activated remotely. All automation objects on a given system may be globally set to "disallow remote activation" or to "allow remote activation". Additionally, and more often, individual objects may be given such capabilities. Remote Automation uses a key in each object's registry settings, AllowRemoteActivation, to determine whether a given server may be activated remotely. If the system-wide settings use this mode, then each object in the registry may be assigned this key, and the individual status of each one may be set to "yes" or "no" as appropriate.

If the server system is running Windows NT, then an alternative form of security is allowed. In this case, Remote Automation uses the NT ACL (access control list) to specify which users or group(s) of users may remotely activate a given server.

Note that the security options apply to the whole object; it is not possible to set attributes of a specific interface, or of individual properties or methods on that object.

All security options may be set through the Remote Automation Connection Manager (commonly referred to as the RAC Manager).