[JBoss JIRA] (WFLY-13780) Initial transformation-based tech preview EE 9 variant of WildFly
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-13780:
---------------------------------------
Summary: Initial transformation-based tech preview EE 9 variant of WildFly
Key: WFLY-13780
URL: https://issues.redhat.com/browse/WFLY-13780
Project: WildFly
Issue Type: Feature Request
Components: Build System, EE, Server
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Produce an initial EE 9 variant of WildFly as described in https://wildfly.org/news/2020/06/23/WildFly-and-Jakarta-EE-9/ and https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/thread/...
This would be intended to be a milestone type release, not expected to pass the EE 9 TCK and likely not passing significant parts of the WildFly testsuite. The basic goal is to provide something to the community to look at and to surface technical issues.
Many dependencies used by this initial version may not be Final releases of the respective components.
Basic goals:
1) Produce an EE 9 variant of the wildfly-ee feature pack.
2) Galleon tooling to produce that feature pack and to provision a server from it that, at provisioning time, transforms any EE 8 (javax.* namespace) artifacts to EE 9 (jakarta.*).
3) Produce a fat server dist from that feature pack.
4) Server should be able to transform EE 8 managed deployments to EE 9 when the management layer accepts the deployment content.
Nice-to-have goals:
1) A variant of the full 'wildfly' feature pack (which brings various MP specs) that depends on the EE 9 wildfly-ee one.
2) Dist based on that.
Non-goals:
1) Thin server distributions.
2) Support for supplemental things like legacy Hibernate versions or JSF integrations beyond the default mojarra.
3) Domain mode support for legacy AS 7 extensions that were replaced in WildFly 8.
4) Support for the legacy security subsystem, picketlink extensions, or agroal.
Other technical points:
The default messaging configuration likely will not be for an embedded broker.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFCORE-5088) User is able to specify credential-reference with only store name
by Jan Stourac (Jira)
[ https://issues.redhat.com/browse/WFCORE-5088?page=com.atlassian.jira.plug... ]
Jan Stourac commented on WFCORE-5088:
-------------------------------------
[~fjuma], thank you for the fix! I've tried your changes and I can confirm that the issue is fixed now. I've also put some comments on the MR itself.
> User is able to specify credential-reference with only store name
> -----------------------------------------------------------------
>
> Key: WFCORE-5088
> URL: https://issues.redhat.com/browse/WFCORE-5088
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jan Stourac
> Assignee: Farah Juma
> Priority: Major
>
> It is possible to create a {{credential-reference}} to the credential store just with the name of credential store in question - without specifying {{alias}} (or {{clear-text}} in case of automatic addition of new record into the credential store, see doc [16.4.2. Automatic Updates of Credential Stores|https://docs.wildfly.org/20/WildFly_Elytron_Security.html#referenc...]). Actual configuration error is revealed when server is reloaded with following error message in server log (note that I can see this error in case of 'key-store' example but not in case of 'imap' example - see Reproduction steps for this issue):
> {code}
> 22:03:26,791 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("key-store" => "exampleKS")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.exampleKS" => "WFLYELY00004: Unable to start the service.
> Caused by: java.io.IOException: WFLYELY00910: Password cannot be resolved for key-store '/tmp/cred/wildfly-20.0.1.Final/standalone/configuration/example.keystore'"}}
> {code}
> This misconfiguration is not possible to do in {{Wildfly 19.1.0.Final}} as you are requested to specify {{alias}} attribute too.
> I suspect that change in behavior has been introduced thanks to this new feature https://issues.redhat.com/browse/WFLY-12218 (see the doc referenced above).
> Correct behavior is to require credential store name and:
> # 'alias'
> # or 'alias' and 'clear-text'
> # or 'clear-text' (alias will be generated automatically in this case)
> as described in the referenced documentation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months