|
|
|
SecureBroker Architecture. A server application uses the security interfaces
to manage the security properties of the objects that were created in its memory space.
Both clients and servers can use the security interfaces to obtain certificates
from a Certificate Authority using the LDAP interface.
The security interfaces are normal CORBA objects with their own IDL
(defined in the CORBASec specification from OMG). Therefore, all of their
communication to external objects uses the ORB core (and hence IIOP).
As in a non-secure ORB, SecureBroker uses IIOP for its communication. The
IIOP messages can be mapped either to the SSL transport mechanism for
secure communication or to the normal TCP/IP transport for non-secure
communication.
SecureBroker works within several Smalltalk development environments:
VisualAge for Smalltalk (IBM); VisualWorks (Cincom); and, any Smalltalk
development environment in which SSLEAY has been implemented including
Windows NT, AIX, Solaris, and Linux. In addition the sources are available
and can be compiled easily on most Unix systems.
SecureBroker was originally developed to interoperate with Orbix/SSL. It
uses the same SSL library as Orbix/SSL(SSLEAY). It has also been
demonstrated to work with VisiBroker which uses a different SSL library.
Back to Top.
|
|
|
|
Products and Tools