May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3383) Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3383?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3383: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency. > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3383 > URL: https://issues.jboss.org/browse/WFCORE-3383 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Darran Lofthouse > Priority: Critical > > This builds on https://issues.jboss.org/browse/WFCORE-1106 so we can skip runtime steps when the dependent services are not available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10348) Picketlink federation XML writer should not rely on the ordering in the ModelNode

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-10348?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-10348: --------------------------------------- Assignee: (was: Darran Lofthouse) > Picketlink federation XML writer should not rely on the ordering in the ModelNode > --------------------------------------------------------------------------------- > > Key: WFLY-10348 > URL: https://issues.jboss.org/browse/WFLY-10348 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Alexey Loubyansky > > AFAICS, FederationSubsystemWriter is relying on the ordering of the children of the root ModelNode when persisting the subsystem configuration. If one was to create a configuration using management operations from scratch, the operations would have to be ordered according to the order of the corresponding elements defined in the XSD schema. Which is not very practical and increases the chance of getting errors that could be avoided by making the writer persist the elements in the valid order. > E.g. in the current implementation if a management operation configuring key-store appeared after the one(s) configuring service-providers the resulting subsystem XML would be invalid according to the XSD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10348) Picketlink federation XML writer should not rely on the ordering in the ModelNode

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-10348?page=com.atlassian.jira.plugin... ] Martin Choma commented on WFLY-10348: ------------------------------------- I have run through security related subsystems and same approach is used in IDMSubsystemWriter. But there is only one child element so it is safe :) > Picketlink federation XML writer should not rely on the ordering in the ModelNode > --------------------------------------------------------------------------------- > > Key: WFLY-10348 > URL: https://issues.jboss.org/browse/WFLY-10348 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Alexey Loubyansky > Assignee: Darran Lofthouse > > AFAICS, FederationSubsystemWriter is relying on the ordering of the children of the root ModelNode when persisting the subsystem configuration. If one was to create a configuration using management operations from scratch, the operations would have to be ordered according to the order of the corresponding elements defined in the XSD schema. Which is not very practical and increases the chance of getting errors that could be avoided by making the writer persist the elements in the valid order. > E.g. in the current implementation if a management operation configuring key-store appeared after the one(s) configuring service-providers the resulting subsystem XML would be invalid according to the XSD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1567) [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1567?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1567: --------------------------------------- If you just make sure both Martin's are away they can discuss this with us. > [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest > --------------------------------------------------------------------------------- > > Key: ELY-1567 > URL: https://issues.jboss.org/browse/ELY-1567 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Rostislav Svoboda > Priority: Critical > > Split of https://issues.jboss.org/browse/WFLY-10256 to component trackers > Artifact wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR as it has overlay directory but no Multi-Release entry in Manifest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1567) [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1567?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse edited comment on ELY-1567 at 5/11/18 7:36 AM: ---------------------------------------------------------------- If you just make sure both Martin's are aware they can discuss this with us. was (Author: dlofthouse): If you just make sure both Martin's are away they can discuss this with us. > [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest > --------------------------------------------------------------------------------- > > Key: ELY-1567 > URL: https://issues.jboss.org/browse/ELY-1567 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Rostislav Svoboda > Priority: Critical > > Split of https://issues.jboss.org/browse/WFLY-10256 to component trackers > Artifact wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR as it has overlay directory but no Multi-Release entry in Manifest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1567) [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/ELY-1567?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda updated ELY-1567: ----------------------------------- Description: Split of https://issues.jboss.org/browse/WFLY-10256 to component trackers Artifact wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR as it has overlay directory but no Multi-Release entry in Manifest was: Split of https://issues.jboss.org/browse/WFLY-10256 to component trackers Artifact wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR as it has overlay directory by no Multi-Release entry in Manifest > [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest > --------------------------------------------------------------------------------- > > Key: ELY-1567 > URL: https://issues.jboss.org/browse/ELY-1567 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Rostislav Svoboda > Priority: Critical > > Split of https://issues.jboss.org/browse/WFLY-10256 to component trackers > Artifact wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR as it has overlay directory but no Multi-Release entry in Manifest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1567) [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/ELY-1567?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda commented on ELY-1567: ---------------------------------------- [~dlofthouse] who can look into this ? > [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest > --------------------------------------------------------------------------------- > > Key: ELY-1567 > URL: https://issues.jboss.org/browse/ELY-1567 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Rostislav Svoboda > Priority: Critical > > Split of https://issues.jboss.org/browse/WFLY-10256 to component trackers > Artifact wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR as it has overlay directory but no Multi-Release entry in Manifest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3831) jboss-cli.ps1 script doesn't return exit value correctly

by Marek Kopecký (JIRA)

Marek Kopecký created WFCORE-3831: ------------------------------------- Summary: jboss-cli.ps1 script doesn't return exit value correctly Key: WFCORE-3831 URL: https://issues.jboss.org/browse/WFCORE-3831 Project: WildFly Core Issue Type: Bug Components: Scripts Reporter: Marek Kopecký Assignee: Kabir Khan jboss-cli.ps1 script doesn't return exit value correctly Steps to reproduce: # start Command prompt in Windows # PowerShell \-ExecutionPolicy Bypass -File jboss-cli.ps1 "\-\-commands=nonsence" \-\-timeout=10000 # echo %ERRORLEVEL% #* "0" is printed, "1" should be printed # add "exit 5" to the end of jboss-cli.ps1 file # PowerShell \-ExecutionPolicy Bypass -File jboss-cli.ps1 "\-\-commands=nonsence" \-\-timeout=10000 # echo %ERRORLEVEL% #* "5" is printed cc: [~jamezp], [~eduda], [~jdenise] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3799) FIPS mode is not detected correctly on JDK 8

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3799?page=com.atlassian.jira.plugi... ] Kabir Khan resolved WFCORE-3799. -------------------------------- Resolution: Done > FIPS mode is not detected correctly on JDK 8 > -------------------------------------------- > > Key: WFCORE-3799 > URL: https://issues.jboss.org/browse/WFCORE-3799 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 5.0.0.Alpha4 > Environment: jdk 8 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 5.0.0.Beta1 > > > Trying SSL in FIPS mode I get "KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used" > {code} > 17:45:32,678 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.security.ssl-context.server-ssl-context: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server-ssl-context: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:926) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:924) > ... 9 more > 17:45:32,686 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("server-ssl-context" => "server-ssl-context") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server-ssl-context" => "java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used"}} > {code} > https://github.com/wildfly/wildfly-core/blob/02e2de734c68e23e0bae81fc12d7... > Debugging revealed problem is in this call > {code:java|title=SSLDefinitions.java} > final Class<?> providerClazz = SSLDefinitions.class.getClassLoader().loadClass("com.sun.net.ssl.internal.ssl.Provider"); > {code} > which ends with ClassNotFoundException > {code} > java.lang.ClassNotFoundException: com.sun.net.ssl.internal.ssl.Provider from [Module "org.wildfly.extension.elytron" version 5.0.0.Alpha-redhat-20180502 from local module loader @41ee392b (finder: local module finder @1e67a849 (roots: /home/mchoma/Repos/tests-security/fips/target/dist/jboss-eap/modules,/home/mchoma/Repos/tests-security/fips/target/dist/jboss-eap/modules/system/layers/base))] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3799) FIPS mode is not detected correctly on JDK 8

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3799?page=com.atlassian.jira.plugi... ] Martin Choma commented on WFCORE-3799: -------------------------------------- I can confirm with jboss modules 1.8.4.Final I don't see the issue anymore. > FIPS mode is not detected correctly on JDK 8 > -------------------------------------------- > > Key: WFCORE-3799 > URL: https://issues.jboss.org/browse/WFCORE-3799 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 5.0.0.Alpha4 > Environment: jdk 8 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 5.0.0.Beta1 > > > Trying SSL in FIPS mode I get "KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used" > {code} > 17:45:32,678 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.security.ssl-context.server-ssl-context: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server-ssl-context: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:926) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:924) > ... 9 more > 17:45:32,686 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("server-ssl-context" => "server-ssl-context") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server-ssl-context" => "java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used"}} > {code} > https://github.com/wildfly/wildfly-core/blob/02e2de734c68e23e0bae81fc12d7... > Debugging revealed problem is in this call > {code:java|title=SSLDefinitions.java} > final Class<?> providerClazz = SSLDefinitions.class.getClassLoader().loadClass("com.sun.net.ssl.internal.ssl.Provider"); > {code} > which ends with ClassNotFoundException > {code} > java.lang.ClassNotFoundException: com.sun.net.ssl.internal.ssl.Provider from [Module "org.wildfly.extension.elytron" version 5.0.0.Alpha-redhat-20180502 from local module loader @41ee392b (finder: local module finder @1e67a849 (roots: /home/mchoma/Repos/tests-security/fips/target/dist/jboss-eap/modules,/home/mchoma/Repos/tests-security/fips/target/dist/jboss-eap/modules/system/layers/base))] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018