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 |
What are the reason to avoid the development of multi-threaded corba application?
What is CORBA?
What is "Principal", and what is meant by "Principal authentication"?
Can corba allow servers to cause client side events or notifications?
Are the any interfaces specified in CORBASEC for controlling security context by security-aware applications?
Explain does corba supports asynchronous communication?
Explain what is corba good for?
How are privacy and non-repudiation addressed by CORBASEC?
Does CORBA security guarantee that the request and reply are not tampered and not intercepted on their way between the client and the target?
Explain are there different threading models that can be used within corba servers?
Explain can corba application have call back?
Compare CORBA security with security of other distributed object computing frameworks such as Java RMI or DCOM?