Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Bound Security Access Data : Binding of Security Access Data

Binding of Security Access Data
The Security Manager performs clearance checks on every access to every object. To perform clearance checks in an unobtrusive manner, the Security Manager copies object permissions into the Execution Environment and leaves them there for future reference.
This method of copying permissions, called binding, enhances performance. The Security Manager continues to refer to the memory-bound copy to validate accesses, until the Execution Environment is recycled or you refresh it with the latest information from the database.
Refreshing Bound Security Access Data
In most cases, security data can be refreshed without logging out of and in to TIBCO Object Service Broker by invoking a tool that rebinds the data.
If the object permissions are changed after they are bound, current users must refresh, or rebind, their security information by doing one of the following:
Call the SEC_REBIND tool from a rule, as in the following example:
CALL SEC_REBIND(NULL,NULL,NULL);
The three arguments supplied with this tool, although not currently used, must be supplied. The example supplied three nulls. This enables a user to refresh the binding without logging out of the system.
If you access the Execution Environment in question through an OSB UI session, in order to pick up the rebound security data, be sure to also close and restart that OSB project after SEC_REBIND has been run.
See Also
TIBCO Object Service Broker Application Administion about binding.
TIBCO Object Service Broker Programming in Rules about rules.
TIBCO Object Service Broker for z/OS Installing and Operating or TIBCO Object Service Broker for Open Systems Installing and Operating about stopping and starting Execution Environments.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved