You can specify the container invoker in the container configuration so you can get
this down to a per-bean setting if you want. Any beans that need encrypted transport
would be assigned to the container with the ssl socket factories.
Any settings of security related stuff like key stores, trusted cert stores, etc. would
be better handled as a mbean in the JBossSX security extension framework. The key
thing is that the JBoss core allow for easy integration of alternate socket
implementations.
Any configuration requirements of the socket implementation should be handled by
the existing JMX mbean integration support.
>
> I made the experiences, that it is not necessary to export every remote
> object which SSL-sockets. so ist would be helpful setting a flag/tag in the
> xml-deployment-file, which bean should use SSL-sockets.
> Furthermore, you should consider having the posssibility, to give in a
> global conf-file the passphrase for the keystore, where all ssl related keys
> and certificates are stored.
>
> so long...
> Daniel
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
