August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1642) Compilation error on JDK 11: cannot find class sun.reflect.Reflection

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1642?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1642: ---------------------------------- Fix Version/s: 1.7.0.CR1 > Compilation error on JDK 11: cannot find class sun.reflect.Reflection > --------------------------------------------------------------------- > > Key: ELY-1642 > URL: https://issues.jboss.org/browse/ELY-1642 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Affects Versions: 1.5.1.Final > Environment: openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+25) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+25, mixed mode) > Reporter: Ondrej Kotek > Priority: Critical > Fix For: 1.7.0.CR1 > > > {{mvn test}} results in compilation error: > {noformat} > [ERROR] /home/okotek/git/wildfly-elytron/src/main/java/org/wildfly/security/manager/WildFlySecurityManager.java:[58,19] cannot find symbol > symbol: class Reflection > location: package sun.reflect > {noformat} > Blocks testing on JDK 11, setting to Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1639: --------------------------------------- It does sound like the alias attribute should be optional, part of the connection establishment is about selecting a certificate the other side can trust so having multiple keys in the key store on a client is still valid - the time to use an alias is when multiple entries could match and we need to filter them. I don't think we want to do it for this PR but we probably should at some point expand the configuration to support the definition a filter so client side multiple entries could still be possible when filtered. > FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used > ------------------------------------------------------------- > > Key: ELY-1639 > URL: https://issues.jboss.org/browse/ELY-1639 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Blocker > Attachments: cli-wildfly-config.xml > > > Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception > {code} > 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost' > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) > ... 5 more > Caused by: java.io.IOException: Failed to obtain SSLContext > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156) > at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222) > ... 8 more > 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.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208) > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153) > ... 10 more > {code} > It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4045) Make ExtensibleHttpManagement.addManagementHandler() return error code 500

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4045?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-4045: ------------------------------- Description: The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change. This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. The standard error page will be updated in WFCORE-4046 to be more generic. was: The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change. This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. > Make ExtensibleHttpManagement.addManagementHandler() return error code 500 > -------------------------------------------------------------------------- > > Key: WFCORE-4045 > URL: https://issues.jboss.org/browse/WFCORE-4045 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Kabir Khan > Assignee: Kabir Khan > > The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change. > This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. The standard error page will be updated in WFCORE-4046 to be more generic. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4046) Make the text in the console error context less console specific.

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-4046: ---------------------------------- Summary: Make the text in the console error context less console specific. Key: WFCORE-4046 URL: https://issues.jboss.org/browse/WFCORE-4046 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Kabir Khan Assignee: Kabir Khan The text currently mentions {quote} However you have not yet added any users to be able to access the admin console. {quote} which is too console specific as we now allow subsystems to register their own handlers via the ExtensibleHttpManagement.addManagementHandler() method. It will be changed to {quote} However you have not yet added any users to be able to access the HTTP management API. {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4045) Make ExtensibleHttpManagement.addManagementHandler() return error code 500

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4045?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-4045: ------------------------------- Component/s: Management > Make ExtensibleHttpManagement.addManagementHandler() return error code 500 > -------------------------------------------------------------------------- > > Key: WFCORE-4045 > URL: https://issues.jboss.org/browse/WFCORE-4045 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Kabir Khan > > The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change. > This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4045) Make ExtensibleHttpManagement.addManagementHandler() return error code 500

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4045?page=com.atlassian.jira.plugi... ] Kabir Khan reassigned WFCORE-4045: ---------------------------------- Assignee: Kabir Khan > Make ExtensibleHttpManagement.addManagementHandler() return error code 500 > -------------------------------------------------------------------------- > > Key: WFCORE-4045 > URL: https://issues.jboss.org/browse/WFCORE-4045 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Kabir Khan > Assignee: Kabir Khan > > The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change. > This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4045) Make ExtensibleHttpManagement.addManagementHandler() return error code 500

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-4045: ---------------------------------- Summary: Make ExtensibleHttpManagement.addManagementHandler() return error code 500 Key: WFCORE-4045 URL: https://issues.jboss.org/browse/WFCORE-4045 Project: WildFly Core Issue Type: Bug Reporter: Kabir Khan The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change. This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-9) Elytron permission-set should throw exception for non-existent permission

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFWIP-9?page=com.atlassian.jira.plugin.sy... ] Farah Juma closed WFWIP-9. -------------------------- Resolution: Duplicate Issue Closing this one since it's a duplicate of WFCORE-3596. > Elytron permission-set should throw exception for non-existent permission > ------------------------------------------------------------------------- > > Key: WFWIP-9 > URL: https://issues.jboss.org/browse/WFWIP-9 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Farah Juma > Labels: WFCORE-3596 > > When non-existent permission (e.g. when there is a typo in class-name) is added to Elytron permission-set then exception should be thrown. It should throw exception for wrong class-name as well as wrong module. > See issue WFCORE-3796 for more details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2888: ------------------------------------- [~stetson.robinson] [~karreiro] I'm hoping we can have an expanded area for detailed explanatory text. I added a quick demo of the View more/ less Help content. [~stetson.robinson] I took some of the Data Type explanations that Guilherme offered on https://issues.jboss.org/browse/DROOLS-2876 and tweaked it for this presentation. I'll send an email with raw text if that helps. Thanks! > Data Type UX - dialog enhancements: Add and Reorder > ---------------------------------------------------- > > Key: DROOLS-2888 > URL: https://issues.jboss.org/browse/DROOLS-2888 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow. > * Reorder the list of Custom data types so that I can arrange data types in a logical order. > * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default. > Functional considerations/ pre conditions: > * Fields will be presented at the bottom of a structured list by default. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > * Drag-n-drop be evaluated with regard to accessibility. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2888: -------------------------------- Attachment: viewMoreLess.gif > Data Type UX - dialog enhancements: Add and Reorder > ---------------------------------------------------- > > Key: DROOLS-2888 > URL: https://issues.jboss.org/browse/DROOLS-2888 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow. > * Reorder the list of Custom data types so that I can arrange data types in a logical order. > * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default. > Functional considerations/ pre conditions: > * Fields will be presented at the bottom of a structured list by default. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > * Drag-n-drop be evaluated with regard to accessibility. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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