![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This chapter is meant for security administrators who are fully aware of the operational requirements for their security environment.You can use the encryption application program interface (API) provided with TIBCO Object Service Broker to facilitate password encryption. This interface is implemented using an encryption loadable module.
• No encryption, by using the default module provided with TIBCO Object Service Broker. Passwords are then left as clear text in the MetaStor.
• Encryption—either one-way or two-way—by replacing the default module with your own encryption loadable module. Sample code that demonstrates how to implement this option appears in install_path/sample/src/encrypt/sample.c for Open Systems, and, for z/OS, in the member HDRSCXIT in the ASM distribution data set supplied with TIBCO Object Service Broker. All components that participate in the storage or transmission of TIBCO Object Service Broker passwords use this interface.
• The initial custom encryption loadable module must support the back-level encryption algorithm supplied with TIBCO Object Service Broker, which is clear text.If you choose to use your own encryption loadable module, the algorithm that you use for encryption can be one-way or two-way. If you choose to implement one-way encryption, the following TIBCO Object Service Broker facilities are unavailable to your users:These facilities require a clear text password and a one-way encryption prevents the decryption that is required to pass back the clear text password.TIBCO Object Service Broker Programming in Rules about rules.TIBCO Object Service Broker Application Administion about @SCHEDULEMODEL.TIBCO Object Service Broker for z/OS External Environments about using IMS TM.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |