next up previous contents
Next: 5.3 VisiBroker Up: 5.2.2 OrbixSecurity Previous: 5.2.2.7 Can we use

5.2.2.8 Authentication Security Exception

  

Extended Question:
When I want the Server to authenticate it self to the Client, or when I want to put a secure invocation policy on the Server, then I get an error message telling me "Authentication Security Exception", "Target is not secure". The opposite is no problem, the Client can authenticate itself to the server.

Is there anybody who have came across this problem, or who have suggestions on how I should solve it?

Gregg Tally
(July, 1998): The error message appears to indicate that the principal for orbixd, host/IT_daemon, does not support authentication when acting as the target. Have you used getnvit to see if host/IT_daemon supports the authentication policy and QoP required by your server and client principals? If not, you can use setnvtit on host/IT_daemon so that orbixd will support authentication when acting as a target.