How does CORBA security affect application writers?
Linda Gricius (March, 1998):
In a secure CORBA system, the same client calls the same
target object that it would call in an unsecured system. The
invocation request is intercepted by the ORB Security
service at both client and target, and the level of
protection required by the current policy settings is
applied. Security may be enforced at the client side, the
target side, or both. This includes support for any or all
of the following:
* Establishing secure associations between the client
and target;
* Integrity and/or confidentiality protection for
individual requests and replies sent between the client and
target;
* Access control checks to determine if the principal is
allowed to perform this operation on the target object;
* Auditing of security-relevant events.
Since the invocation is intercepted in the ORB, it is
transparent to the application. However, applications that
want to enforce their own security controls can call on the
Security services directly.
It's important to note that object implementations do not
need to be changed to fit into and be protected by a secure
ORB. A distributed application may be made up of many small
objects, and it is unusual for all the application
developers to be sufficiently security knowledgeable to make
the right calls on the security facilities.
| Is This Answer Correct ? | 0 Yes | 0 No |
Explain does corba supports asynchronous communication?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?
What's CORBA Security Service?
Are there any upcoming updates of the CORBA specification?
Does CORBA security guarantee that the request and reply are not tampered and not intercepted on their way between the client and the target?
What is CORBA?
What are the protocols used by CSI?
What are the primary differences between RMI and CORBA?
Compare CORBA security with security of other distributed object computing frameworks such as Java RMI or DCOM?
What is available in CORBASEC for strong (writer-to-reader) authentication?
Does corba support distributed reference counting architectures?
Are CORBAsec implementations from the US generally subjected to export control?