> Enabling Access Control
> Administrators can enable or disable access control for the server. Administrators can also enable and disable permission checking for specific destinations.
> Server Control
> The property in the main configuration file enables or disables the checking of permissions for all destinations managed by the server. The authorization property also enables or disables verification of user names and passwords.

> | The default setting is disabled. For secure deployments, the administrator must explicitly set authorization to enabled.

> When authorization is disabled, the server grants any connection request, and does not check permissions when a client accesses a destination (for example, publishing a message to a topic).
> When authorization is enabled, the server grants connections only from valid authenticated users. The server checks permissions for client operations involving secure destinations.
> To enable authorization, either edit tibemsd.conf (set the authorization property to enabled, and restart the server). Or you can use the tibemsadmin tool to dynamically enable authorization with the following set server command:
> set server authorization=enabled
> Authorization does affect connections between fault-tolerant server pairs; see Authorization and Fault-Tolerant Servers.
> Administrators must always log in with the correct administration username and password to perform any administrative function—even when authorization is disabled.
> Destination Control
> When server authorization is enabled, the server checks user names and password of all connections without exceptions. However, operations on destinations, such as sending a message or receiving a message, are not verified unless the destination has enabled the secure property on the destination. All operations by applications on the destination with secure enabled are verified by the server according to the permissions listed in acl.conf. Destinations with secure disabled continue to operate without any restrictions.

> | The secure property is independent of SSL-level security. The secure property controls only basic authentication and permission verification. It does not affect the security of communication between clients and server.

> When a destination does not have the secure property set, any authenticated user can perform any actions on that topic or queue.
> See Destination Properties for more information about destination properties.

Copyright © TIBCO Software Inc. All Rights Reserved.