# secure

When the `secure` property is enabled for a destination, it instructs the server to check user permissions whenever a user attempts to perform an operation on that destination.

You can set secure using the form:

       secure

If the `secure` property is not set for a destination, the server does not check permissions for that destination and any authenticated user can perform any operation on that topic or queue.

Note: The `secure` property is independent of SSL—it controls basic authentication and permission verification within the server. To configure secure communication between clients and server, see SSL Protocol.

The server `authorization` property acts as a master switch for checking permissions. That is, the server checks user permissions on secure destinations only when the `authorization` property is enabled. To enforce permissions, you must both enable the authorization configuration parameter, and set the `secure` property on each affected destination.

See Authentication and Permissions for more information on permissions and the secure property.

Copyright © Cloud Software Group, Inc. All rights reserved.