[teiid-issues] [JBoss JIRA] Resolved: (TEIID-404) 1-way and 2-way SSL to MMx must support different keystore file names within a cluster

Tue Oct 6 13:43:49 EDT 2009

     [ https://jira.jboss.org/jira/browse/TEIID-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-404.
----------------------------------

    Resolution: Out of Date

SSL configuration is now in the deploy.properties, which would be configured for each cluster member.

> 1-way and 2-way SSL to MMx must support different keystore file names within a cluster
> --------------------------------------------------------------------------------------
>
>                 Key: TEIID-404
>                 URL: https://jira.jboss.org/jira/browse/TEIID-404
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 6.1.0
>            Reporter: Larry O'Leary
>             Fix For: 6.3
>
>
> Defect Tracker #24283: File naming conventions require a keystore file to be prefixed with the machine's host name. This creates a problem when deploying certificates for use with SSL to a MetaMatrix System as the keystore on each MetaMatrix Server has a different name. Currently, the MMConsole only allows you to set a key store file name that will be used system wide. 
> We will need the ability to define a key store file name on a per host and possibly a per VM basis. This could be accomplished in many different manners. 
> The recommended implementation would be to simply move the SSL Resource configuration to the process and host level. This would allow an administrator to continue to use the Console to configure SSL. 
> At the host level, the administrator could set the default key store file name to be used for all VM(s) deployed to that host.  At the VM level, the administrator could set a key store file name value that will override the default host level key store file name property.  
> This should also be done for the client trust store property to support 2-way SSL.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira