![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Authentication: the Trusted security model does not guarantee the authenticity of the request.
• Integrity: the Trusted security model does not guarantee the integrity of the request.
• Authorization: the Trusted security model guarantees that only authorized users can perform restricted actions.
• Privacy: the Trusted security model does not address the privacy of the request. All requests are sent using plain text.Users are explicitly granted or denied access through the access control file. A user who is not in this file is not allowed to perform any operations on the TIBCO Hawk system. Access control information is in a plain ASCII file located in the HAWK_HOME/examples/security folder.All trusted requests (both Trusted and TrustedWithDomain) can be logged to rolling log files in a directory of your choice.The current log file is named Trusted.log. When it reaches the maximum size (size), it is closed and renamed Trusted1.log, and a new Trusted.log is started. When the number of logs exceeds the maximum (n), log entries roll over to reuse the oldest log file.
• To allow access to a user who starts Hawk Display (or the Console API application) in Trusted security mode, the entry for <user> specified in the agent’s Trusted.txt or TrustedWithDomain.txt should not include the domain of the user who actually starts Hawk Display (or the Console API application).
• To allow access to a user who starts Hawk Display in TrustedWithDomain security mode, the entry for <user> specified in the agent’s Trusted.txt or TrustedWithDomain.txt should include the domain of the user who actually starts Hawk Display.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |