May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2528) Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2528?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2528: ------------------------------- Fix Version/s: 3.0.0.Beta21 (was: 3.0.0.Beta20) > Clean up testsuite Elytron registration -- VaultPasswordsInCLITestCase > ---------------------------------------------------------------------- > > Key: WFCORE-2528 > URL: https://issues.jboss.org/browse/WFCORE-2528 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta21 > > > Leftover cleanup from WFCORE-1958 since VaultPasswordsInCLITestCase is not enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2786) Improve the composition operation output

by Filippe Spolti (JIRA)

Filippe Spolti created WFCORE-2786: -------------------------------------- Summary: Improve the composition operation output Key: WFCORE-2786 URL: https://issues.jboss.org/browse/WFCORE-2786 Project: WildFly Core Issue Type: Enhancement Components: CLI Reporter: Filippe Spolti When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N. I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example: Payload: {quote} { "address": [], "json.pretty": 1, "operation": "composite", "steps": [ { "name": "server-state", "operation": "read-attribute" }, { "address": { "deployment": "*" }, "name": "status", "operation": "read-attribute" } ] } {quote} Response: {quote} { "outcome": "success", "result": { "step-1": { "outcome": "success", "result": "running" }, "step-2": { "outcome": "success", "result": [] } } } {quote} If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload. It will be great if we can add a extra field in the response or change the steps name to its operation name, for example: {quote} { "outcome": "success", "result": { "step-1": { "operation-name": "server-state", "outcome": "success", "result": "running" }, "step-2": { "operation-name": "deployment-info", "outcome": "success", "result": [] } } } {quote} Or {quote} { "outcome": "success", "result": { "server-state": { "outcome": "success", "result": "running" }, "deployment-info": { "outcome": "success", "result": [] } } } {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2483) There is missing CS integration with core management

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2483?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2483: ------------------------------- Fix Version/s: 3.0.0.Beta20 > There is missing CS integration with core management > ---------------------------------------------------- > > Key: WFCORE-2483 > URL: https://issues.jboss.org/browse/WFCORE-2483 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 3.0.0.Beta20 > > > Priority is BLOCKER because this issue blocks RFE verification https://issues.jboss.org/browse/EAP7-538 > There must be credential store integration with core management as is mentioned in requirements of RFE. > *management/security-realm* > *management/security-realm/authentication/truststore* keystore-password > *management/security-realm/server-identity/ssl* key-password and keystore-password > *management/security-realm/server-identity/secret* > *management/security-realm/authentication/users* > But *security-realm* is deprecated, these resources have this description: > {code} > The security-realm configuration is deprecated and may be removed or moved in future versions. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8738) Update openjdk corba to work with JDK9

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8738: --------------------------------- Summary: Update openjdk corba to work with JDK9 Key: WFLY-8738 URL: https://issues.jboss.org/browse/WFLY-8738 Project: WildFly Issue Type: Sub-task Components: IIOP Reporter: Tomaz Cerar Assignee: Tomasz Adamski Currently running IIOP tests explodes with {noformat} Caused by: java.lang.NoClassDefFoundError: sun/reflect/ReflectionFactory$GetReflectionFactoryAction at javax.orb.api//sun.corba.Bridge.<init>(Bridge.java:154) at javax.orb.api//sun.corba.Bridge.get(Bridge.java:176) at javax.orb.api//com.sun.corba.se.impl.io.ObjectStreamClass$1.run(ObjectStreamClass.java:93) at javax.orb.api//com.sun.corba.se.impl.io.ObjectStreamClass$1.run(ObjectStreamClass.java:91) ... {noformat} Which is caused by some changes in package names in sun.reflect.* classes. David's proposal is that we probably need to port https://github.com/dmlloyd/openjdk/commit/cc27408ff6d7f61b401211d37843117... https://github.com/dmlloyd/openjdk/commit/142fd225713d19b972a4a6dfa84a601... https://github.com/dmlloyd/openjdk/commit/dec9380008f083f76fe05be0c9bf3f8... commits from upstream to our fork. But some of them might need to be ported to multi version jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8737) Add Elytron SASL tests using JMS client

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8737?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-8737: --------------------------------- Assignee: Josef Cacek (was: Darran Lofthouse) > Add Elytron SASL tests using JMS client > --------------------------------------- > > Key: WFLY-8737 > URL: https://issues.jboss.org/browse/WFLY-8737 > Project: WildFly > Issue Type: Task > Components: Security, Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Add Elytron tests for various SASL mechanisms using JMS client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8737) Add Elytron SASL tests using JMS client

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8737: --------------------------------- Summary: Add Elytron SASL tests using JMS client Key: WFLY-8737 URL: https://issues.jboss.org/browse/WFLY-8737 Project: WildFly Issue Type: Task Components: Test Suite, Security Reporter: Josef Cacek Assignee: Darran Lofthouse Add Elytron tests for various SASL mechanisms using JMS client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2784) Host controller should allow passing jvm parameters to servers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2784?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2784: ------------------------------------------ The server vm config needs to come via the <jvm> element; we don't want it being controlled by the HC VM settings, as the server can be running a completely different JDK from the HC. And trying to intelligently mix the two sounds like a bug nest. But being clever about ignoring stuff that we know won't work makes sense if we can. I forget how the permgen/metaspace stuff worked (i.e. how the HC knew the server's VM version) but it seems like it must have since it's the same kind of problem. > Host controller should allow passing jvm parameters to servers > -------------------------------------------------------------- > > Key: WFCORE-2784 > URL: https://issues.jboss.org/browse/WFCORE-2784 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Brian Stansberry > > It should be possible passing jvm options from host controller to servers runing in it. > One such example is passing -ea to servers if passed to host controller > other example is passing JDK9 specific parameters trough > idea of implementation https://github.com/wildfly/wildfly-core/pull/2394/commits/d824be5c6d973e4... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1147) Coverity: Elytron defect: Unguarded read in VaultCredentialStore class

by Josef Cacek (JIRA)

Josef Cacek created ELY-1147: -------------------------------- Summary: Coverity: Elytron defect: Unguarded read in VaultCredentialStore class Key: ELY-1147 URL: https://issues.jboss.org/browse/ELY-1147 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Critical Coverity scan discovered unguarded read in method {{VaultCredentialStore.getAliases}}. The accessing {{data}} field should be synchronized in the same way as the other usages of this Map. https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=17825... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1146) Coverity: Elytron defect: control flow issue in ServerAuthenticationContext

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-1146?page=com.atlassian.jira.plugin.s... ] Josef Cacek reassigned ELY-1146: -------------------------------- Assignee: Josef Cacek (was: Darran Lofthouse) > Coverity: Elytron defect: control flow issue in ServerAuthenticationContext > --------------------------------------------------------------------------- > > Key: ELY-1146 > URL: https://issues.jboss.org/browse/ELY-1146 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Critical > > The "if" conditions in the Elytron's {{ServerAuthenticationContext.assignName}} are wrong (copy/paste issue): > https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=17824... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1146) Coverity: Elytron defect: control flow issue in ServerAuthenticationContext

by Josef Cacek (JIRA)

Josef Cacek created ELY-1146: -------------------------------- Summary: Coverity: Elytron defect: control flow issue in ServerAuthenticationContext Key: ELY-1146 URL: https://issues.jboss.org/browse/ELY-1146 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Critical The "if" conditions in the Elytron's {{ServerAuthenticationContext.assignName}} are wrong (copy/paste issue): https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=17824... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2017