|
|
|
Porting from SmalltalkBroker. Enabling applications that were developed
using SmalltalkBroker to work with SecureBroker is straightforward (The security
aspect is entirely independent of the IDL and the implementations of the server objects):
- Determine which server objects should use secure communication and the
security needs of each.
- Create a domain manager for secure objects. You can create any number
of domain managers, each with unique security policies.
- Add objects to the correct domain manager. As objects are created on
the server, they must be added to one (or more) of the domain managers. The
domain(s) of each will determine how their security is managed. Any object
not added to a domain is added to the default domain, which has, by
default, no security (although this condition can be changed).
- Run your server application as you would normally. Security will be
managed by the domain managers for each of the server objects created.
Secure Client Applications
A client application written for SmalltalkBroker should function without
any changes to the client side application per se. It will have to be able
to authenticate the server and it will have to be authenticated to the
server if client side authentication is requested. These operations will be
performed automatically by the ORB. However, the client will need to load
a Certificate Authority that it trusts.
Back to Top.
|
|
|
|
Products and Tools