[jboss-jira] [JBoss JIRA] (WFLY-8615) Unable to process received public key with ASYM_ENCRYPT
Paul Ferraro (JIRA)
issues at jboss.org
Thu Apr 20 10:34:00 EDT 2017
[ https://issues.jboss.org/browse/WFLY-8615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro moved JBEAP-10469 to WFLY-8615:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8615 (was: JBEAP-10469)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR16)
Affects Testing: (was: Regression)
> Unable to process received public key with ASYM_ENCRYPT
> -------------------------------------------------------
>
> Key: WFLY-8615
> URL: https://issues.jboss.org/browse/WFLY-8615
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> After starting a two server cluster with ASYM_ENCRYPT, the servers establish a view and then fail to send any more messages, because those can't be decrypted. One of the servers logs the following:
> {noformat}
> 15:29:42,058 WARN [org.jboss.as.clustering.jgroups.protocol.ASYM_ENCRYPT] (thread-14) node2: unable to process received public key
> {noformat}
> The servers throw ReplicationTimeoutExceptions after some timeout period.
> I'm using the following configuration for the Elytron key-store and ASYM_ENCRYPT:
> {noformat}
> /subsystem=elytron/key-store=jgroups-udp2:add(type=jks,path=/tmp/key3.keystore,credential-reference={clear-text=password}, required=true)
> /subsystem=jgroups/stack=udp2/protocol=ASYM_ENCRYPT:add(key-store=jgroups-udp2,key-alias=alias,credential-reference={clear-text=password})
> {noformat}
> and the following command to create the key stores:
> {noformat}
> keytool -genkeypair -alias alias -keypass password -storepass password -storetype jks -keystore key3.keystore -keyalg RSA
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list