Are the any interfaces specified in CORBASEC for
controlling security context by security-aware
applications?
Answer Posted / rithi
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 |
Post New Answer View All Answers
Can corba allow servers to cause client side events or notifications?
What are the reason to avoid the development of multi-threaded corba application?
Compare CORBA security with security of other distributed object computing frameworks such as Java RMI or DCOM?
What is corba? What does it do?
Explain are the different threading models that can be used within corba servers?
Give us high-level technical overview of corba?
What are the shortcomings of CORBA Security service?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?
What is corba good for?
Explain can corba allow servers to cause client side events or notifications?
Explain the reason to implement a corba application with multi-threading?
Can corba application have call back?
Explain are there important forms of asynchronous communication that are not supported directly by corba?
Explain are there different threading models that can be used within corba servers?
Explain what is corba good for?