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 |
Can corba application be tuned for better performance?
Explain can corba application be tuned for better performance?
What are the reason to avoid the development of multi-threaded corba application?
How to come up with application security design using CORBA Security service?
Are the any interfaces specified in CORBASEC for controlling security context by security-aware applications?
Tell me can corba application be multi-threaded?
What are the shortcomings of CORBA Security service?
Can corba application be multi-threaded?
What about CSI with SSL?
Explain are there important forms of asynchronous communication that are not supported directly by corba?
What are the protocols used by CSI?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?