[jboss-jira] [JBoss JIRA] (WFLY-8269) Encrypt-protocol can not be used without Elytron

[Paul Ferraro (JIRA)]

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

Paul Ferraro moved JBEAP-9225 to WFLY-8269:
-------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8269  (was: JBEAP-9225)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                           (was: Clustering)
    Affects Version/s:     (was: 7.1.0.DR12)
      Affects Testing:   (was: Regression)


> Encrypt-protocol can not be used without Elytron
> ------------------------------------------------
>
>                 Key: WFLY-8269
>                 URL: https://issues.jboss.org/browse/WFLY-8269
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Blocker
>
> When we tried to configure UDP stack in JGroups subsystem, we added ASYM_ENCRYPT protocol. According to the model definition attributes "key-store" and "key-alias" together with "credential-reference" child element had to be defined as well. Due to this configuration server failed to start with errors:
> {code}
> ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=jgroups/stack=udp/protocol=ASYM_ENCRYPT' are not available:
>     org.wildfly.security.key-store.server.keystore; There are no known registration points which can provide this capability.
> FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> We should still be able to define original protocol behaviour without Elytron, but it seems we can not use encrypt-protocol without keystore definition in Elytron which could be a backward compatibility issue.
> Used configuration in standalone-ha.xml is attached.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)