What is available in CORBASEC for strong (writer-to-reader)
authentication?
David Chizmadia
(September, 1998)18 : The CORBA Security Specification
(CORBAsec) currently give apps the ability to indicate that
they want the ORB to establish a mutually authenticated
connection between a client object and a target object. The
strength of the mutual authentication is determined by a
policy set by the ORB security administrator and optionally
overriden by the application.
| Is This Answer Correct ? | 0 Yes | 0 No |
Explain does corba define high level application architectures?
Are the any interfaces specified in CORBASEC for controlling security context by security-aware applications?
Does corba define high level application architectures?
What's the difference between CORBA Security Service and CORBASEC?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?
What are the shortcomings of CORBA Security service?
Explain can corba allow servers to cause client side events or notifications?
What are the reason to avoid the development of multi-threaded corba application?
What ORBs claim to have security functionality?
How does CORBA security affect application writers?
Tell me can corba application be multi-threaded?
How to come up with application security design using CORBA Security service?