[teiid-issues] [JBoss JIRA] Resolved: (TEIID-548) When a cluster node added the original certificate is not being copied
Ramesh Reddy (JIRA)
jira-events at lists.jboss.org
Wed May 6 13:44:46 EDT 2009
[ https://jira.jboss.org/jira/browse/TEIID-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Reddy resolved TEIID-548.
--------------------------------
Resolution: Done
Moved the generation of the keystore only for the main server, and for secondary cluster node servers, the keystore is retrieved using the admin api and saved to the config directory.
> When a cluster node added the original certificate is not being copied
> ----------------------------------------------------------------------
>
> Key: TEIID-548
> URL: https://jira.jboss.org/jira/browse/TEIID-548
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 6.1.0
>
>
> Cluster host setup is not copying the keystore certificate from the original host to the newly added cluster node. Now that "JGroups" messages are by default encrypted, not having this will result in node not being joined in the cluster as JGroups discards any messages it gets with wrong keystore.
--
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
More information about the teiid-issues
mailing list