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 |
Tell me can corba application be multi-threaded?
Explain can corba application have call back?
Explain the reason to implement a corba application with multi-threading?
Explain what is the reason to implement corba in client application application?
What are the primary differences between RMI and CORBA?
How does corba support interoperability?
What are the reason to avoid the development of multi-threaded corba application?
What is "Principal", and what is meant by "Principal authentication"?
What are the shortcomings of CORBA Security service?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?
Explain what is corba good for?
What about CSI with SSL?