|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
TIBCO Hawk HTTP Adapter implements a Trusted model of authorization, similar to TIBCO Hawk Display. Refer to Chapter 8, Security, in TIBCO Hawk Installation and Configuration, for more information.
When the security model is implemented on two applications (such as, Hawk HTTP Adaptor and Hawk WebConsole), then it is recommended that each application is deployed on a different instance of the web container (such as, Tomcat).To enable all TIBCO Hawk domains monitored by TIBCO Hawk HTTP Adapter to use the Trusted model, perform the following steps:
2. Open the file HAWK_HOME/webconsole/tomcat/webapps/http/xsl/http/WEB-INF/classes/DomainTransportCfg.xml for editing.
3. Specify the security policy for a particular domain under the <hk::SecurityPolicy> tag.On Microsoft Windows, if HawkTrustedUserId.dll is not in the path of the Web server or application server, the following error message appears in the server’s log file:2003-05-15 12:04:48 Agents: Using Security Policy: COM.TIBCO.hawk.security.trusted.Trusted 2003-05-15 12:04:48 Agents: java.lang.UnsatisfiedLinkError: no HawkTrustedUserID in java.library.pathERROR : Unable to load HawkTrustedUserID - no HawkTrustedUserID in java.library. path ## Thu May 15 12:04:48 PDT 2003 ##If you are implementing your own Java Security class instead of using Trusted implementation (discussed in Chapter 6 of the TIBCO Hawk Programmer’s Guide), you must specify the class in web.xml and the SecurityPolicy element file. Also make this class available to TIBCO Hawk HTTP Adapter.The Java class file can be jarred and copied to HAWK_HOME/webconsole/tomcat/webapps/http/xsl/http/WEB-INF/lib. Restart the Web server or application server to make the new change effective.
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |