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 is the reason to implement corba in client application application?
Can corba application have call back?
What is available in CORBASEC for strong (writer-to-reader) authentication?
What are the reason to avoid the development of multi-threaded corba application?
What are the primary differences between RMI and CORBA?
What ORBs claim to have security functionality?
Can we modify an object in CORBA?
Does the existing Authorization Service of CORBASec scale in a "well" distributed-object environment?
Explain high-level technical overview of corba?
Does corba support distributed reference counting architectures?
What's CORBASEC?
Explain how does corba support interoperability?