JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Feature request JPPF-294  -  Ability for individual connection pools to specify whether they use SSL
Posted Jul 25, 2014 - updated Aug 17, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
  • Assigned to
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 5.0
Issue description
Currently, the client configuration only allows all connections to be secure or all connections to be non-secure. We should provide the ablity to determine secure vs. non-secure for each individual connection pool. This should be specified in the configuration with "driver_name.jppf.ssl.enabled = true | false". If the requested type of connection is not available on the server, the client should be informed during the handshake, discard the connection pool, and issue a warning.

For auto-discovered connection pools, the information is provided with "jppf.ssl.enabled = true | false" in the client configuration. In this case, care must be taken to check that the desired type of connection is available on the server (i.e. whether the information broadcast by the server contains a plain or ssl port as required). If the server information doesn't match, no connection should be attempted and a warning should be issued.

We shall keep a single key store and trust store for the SSL configuration: each store will contain multiple private keys / certificates if needed. This way, a single ssl configuration is needed for all connection pools.

Comment posted by
Aug 17, 06:54
implemented in trunk revision 3335