August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4067) Add the ability for the CLI SSL security commands to be able to obtain a server certificate from Let's Encrypt

by Farah Juma (JIRA)

Farah Juma created WFCORE-4067: ---------------------------------- Summary: Add the ability for the CLI SSL security commands to be able to obtain a server certificate from Let's Encrypt Key: WFCORE-4067 URL: https://issues.jboss.org/browse/WFCORE-4067 Project: WildFly Core Issue Type: Feature Request Components: CLI Reporter: Farah Juma Assignee: Jean-Francois Denise WFCORE-3447 introduced high-level security commands ({{ssl enable-ssl-management}} and {{ssl enable-ssl-http-server}}) for enabling one-way and two-way SSL easily. To generate the server certificate, these high-level security commands made use of key-store management operations to generate a self-signed certificate. Since it is [now possible|WFCORE-3396] to obtain certificates from the Let's Encrypt certificate authority using the CLI, the high-level security commands should be updated so that in addition to being able to generate a self-signed server certificate, they can also obtain a server certificate from Let's Encrypt. Details on the new management operations for obtaining and managing certificates from Let's Encrypt can be found [here|https://developer.jboss.org/wiki/AnalysisDesign-IntegrationWithTheLe...]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4039) Fix JvmOptionsBuilderFactory JDK decision logic

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4039?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4039: ----------------------------------- Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR2) > Fix JvmOptionsBuilderFactory JDK decision logic > ----------------------------------------------- > > Key: WFCORE-4039 > URL: https://issues.jboss.org/browse/WFCORE-4039 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: blocker-WF14, jdk11 > Fix For: 6.0.0.CR5 > > > JvmOptionsBuilderFactory uses wrong JDK to detect if server is going to be running on JDK8 or above. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4039) Fix JvmOptionsBuilderFactory JDK decision logic

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4039?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4039: ----------------------------------- Labels: blocker-WF14 jdk11 (was: ) > Fix JvmOptionsBuilderFactory JDK decision logic > ----------------------------------------------- > > Key: WFCORE-4039 > URL: https://issues.jboss.org/browse/WFCORE-4039 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: blocker-WF14, jdk11 > Fix For: 6.0.0.CR5 > > > JvmOptionsBuilderFactory uses wrong JDK to detect if server is going to be running on JDK8 or above. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4039) Fix JvmOptionsBuilderFactory JDK decision logic

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4039?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4039: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3461 > Fix JvmOptionsBuilderFactory JDK decision logic > ----------------------------------------------- > > Key: WFCORE-4039 > URL: https://issues.jboss.org/browse/WFCORE-4039 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: blocker-WF14, jdk11 > Fix For: 6.0.0.CR5 > > > JvmOptionsBuilderFactory uses wrong JDK to detect if server is going to be running on JDK8 or above. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4049) Deactivate modular jdk properties we used in the past for workarounds.

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4049?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4049: ----------------------------------- Labels: jdk11 (was: ) > Deactivate modular jdk properties we used in the past for workarounds. > ---------------------------------------------------------------------- > > Key: WFCORE-4049 > URL: https://issues.jboss.org/browse/WFCORE-4049 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: jdk11 > Fix For: 6.0.0.CR5 > > > In the past we used the following properties: > -Dsun.util.logging.disableCallerCheck=true > -Djdk.attach.allowAttachSelf=true > to activate some workarounds on modular JDKs. > These workarounds are not needed anymore. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4000) Domain tests fail on JDK11 because of missing java.se module

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4000?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4000: ----------------------------------- Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR2) > Domain tests fail on JDK11 because of missing java.se module > ------------------------------------------------------------ > > Key: WFCORE-4000 > URL: https://issues.jboss.org/browse/WFCORE-4000 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: blocker-WF14, jdk11 > Fix For: 6.0.0.CR5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4049) Deactivate modular jdk properties we used in the past for workarounds.

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4049?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4049: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3461 > Deactivate modular jdk properties we used in the past for workarounds. > ---------------------------------------------------------------------- > > Key: WFCORE-4049 > URL: https://issues.jboss.org/browse/WFCORE-4049 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.CR5 > > > In the past we used the following properties: > -Dsun.util.logging.disableCallerCheck=true > -Djdk.attach.allowAttachSelf=true > to activate some workarounds on modular JDKs. > These workarounds are not needed anymore. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4001) Eliminate --illegal-access option from WildFly

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4001?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4001: ----------------------------------- Labels: blocker-WF14 jdk11 (was: ) > Eliminate --illegal-access option from WildFly > ---------------------------------------------- > > Key: WFCORE-4001 > URL: https://issues.jboss.org/browse/WFCORE-4001 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: blocker-WF14, jdk11 > Fix For: 6.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4000) Domain tests fail on JDK11 because of missing java.se module

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4000?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4000: ----------------------------------- Labels: blocker-WF14 jdk11 (was: ) > Domain tests fail on JDK11 because of missing java.se module > ------------------------------------------------------------ > > Key: WFCORE-4000 > URL: https://issues.jboss.org/browse/WFCORE-4000 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Labels: blocker-WF14, jdk11 > Fix For: 6.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-3962: ----------------------------------- Affects Version/s: (was: 6.0.0.Alpha3) > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFCORE-3962 > URL: https://issues.jboss.org/browse/WFCORE-3962 > Project: WildFly Core > Issue Type: Bug > Components: Management, Modules, Scripts > Reporter: Matej Novotny > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14 > Fix For: 6.0.0.CR5 > > > As per request, copying MODULES-372 to WFCORE as well. > *Affected scripts* > \[standalone|domain|add-user|appclient|jboss-cli|jdr|vault|wsconsume|wsprovide\].\[bat|sh|ps1\] > *Logs* > Starting WFLY with JDK 11 using {{standalone.sh}} yields: > {code} > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > {code} > Output of {{java -version}}: > {code} > openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+21) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018