Are the any interfaces specified in CORBASEC for
controlling security context by security-aware
applications?
Extended Question:
Examples of controlling security context could be the
following:
* Switch context, a possibility of "switching
context service" between already established contexts
* Hold-on context in case of mobility
* Close/take-down context
* Re-establish context after hold-on context service
* Refresh context in case of revocation or as the
same operation as Refresh() in SecurityContext
| Is This Answer Correct ? | 0 Yes | 0 No |
What are the protocols used by CSI?
What is CORBA?
How does CORBA security affect application writers?
What is corba? What does it do?
Explain high-level technical overview of corba?
Explain can corba application have call back?
What is "Principal", and what is meant by "Principal authentication"?
Explain some reason to avoid the development of multi-threaded corba application?
Explain are there different threading models that can be used within corba servers?
What's the difference between CORBA Security Service and CORBASEC?
How does corba support interoperability?
Can corba allow servers to cause client side events or notifications?