April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2433) Autocomplete doesn't work properly in credential-reference.store attribute.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2433?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2433: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Autocomplete doesn't work properly in credential-reference.store attribute. > --------------------------------------------------------------------------- > > Key: WFCORE-2433 > URL: https://issues.jboss.org/browse/WFCORE-2433 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Brian Stansberry > Fix For: 3.0.0.Beta14 > > > Autocomplete doesn't work properly in credential-reference attribute. > I want to use autocomplete for credential-reference.store but it doesn't work. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs1:add(uri="cr-store://test/cs1.jceks", credential-reference={store=<TAB> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2609) CLIRolloutPlanTestCase hang

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2609?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2609: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > CLIRolloutPlanTestCase hang > --------------------------- > > Key: WFCORE-2609 > URL: https://issues.jboss.org/browse/WFCORE-2609 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Priority: Critical > Fix For: 3.0.0.Beta14 > > > Hang: > https://ci.wildfly.org/viewLog.html?buildId=53176&buildTypeId=WF_MasterWi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2589) Eliminate MSC OPTIONAL dependencies usage

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2589?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2589: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Eliminate MSC OPTIONAL dependencies usage > ----------------------------------------- > > Key: WFCORE-2589 > URL: https://issues.jboss.org/browse/WFCORE-2589 > Project: WildFly Core > Issue Type: Task > Affects Versions: 3.0.0.Beta11 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 3.0.0.Beta14 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2585) Servers in domain don't start if management interfaces are bound to all IPv4 addresses

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2585?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2585: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Servers in domain don't start if management interfaces are bound to all IPv4 addresses > -------------------------------------------------------------------------------------- > > Key: WFCORE-2585 > URL: https://issues.jboss.org/browse/WFCORE-2585 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Beta11 > Reporter: Pavel Jelinek > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 3.0.0.Beta14 > > Attachments: host-controller.log, server-one.log > > > This is regression compared to EAP 7.0.0. > See attached logs server-one.log , host-controller.log > {code} > ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://0.0.0.0:9999. The connection failed > at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://0.0.0.0:9999. The connection failed > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:121) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) > at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110) > at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) > ... 4 more > Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (JBOSS-LOCAL-USER, DIGEST-MD5) are supported > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:426) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:465) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:427) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:415) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:177) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:113) > ... 9 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2578) Add ability to configure bind address for outbound XNIO connections

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2578?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2578: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Add ability to configure bind address for outbound XNIO connections > ------------------------------------------------------------------- > > Key: WFCORE-2578 > URL: https://issues.jboss.org/browse/WFCORE-2578 > Project: WildFly Core > Issue Type: Enhancement > Components: IO > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta14 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[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.Beta14 (was: 3.0.0.Beta13) > 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.Beta14 > > > Leftover cleanup from WFCORE-1958 since VaultPasswordsInCLITestCase is not enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2614) Elytron SecurityRealm included more times in a SecurityDomain breaks the domain service

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2614?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2614: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Elytron SecurityRealm included more times in a SecurityDomain breaks the domain service > --------------------------------------------------------------------------------------- > > Key: WFCORE-2614 > URL: https://issues.jboss.org/browse/WFCORE-2614 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta12 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: eap71_beta, management-model, security-domain > Fix For: 3.0.0.Beta14 > > > Elytron subsystem allows to add the same realm more times into a single security domain. Nevertheless in such case domain stops to work with following error message: > {noformat} > 16:14:17,411 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "ManagementDomain") > ]) - failure description: "WFLYELY00002: Can not inject the same realm 'local' in a single security domain." > {noformat} > If such the changed domain is ManagementDomain, then the server stops to start at all. > *Suggested fix* > * either allow to have the same realm in a security domain more times > * or check for duplicate realms already when adding/changing the domain -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2612) Upgrade WildFly Common to 1.2.0.Beta9

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2612?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2612: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Upgrade WildFly Common to 1.2.0.Beta9 > ------------------------------------- > > Key: WFCORE-2612 > URL: https://issues.jboss.org/browse/WFCORE-2612 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta14 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2611) Upgrade WildFly Client Config to 1.0.0.Beta3

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2611?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2611: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Upgrade WildFly Client Config to 1.0.0.Beta3 > -------------------------------------------- > > Key: WFCORE-2611 > URL: https://issues.jboss.org/browse/WFCORE-2611 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta14 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2610) Upgrade XNIO to 3.5.0.Beta4

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2610?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2610: ------------------------------- Fix Version/s: 3.0.0.Beta14 (was: 3.0.0.Beta13) > Upgrade XNIO to 3.5.0.Beta4 > --------------------------- > > Key: WFCORE-2610 > URL: https://issues.jboss.org/browse/WFCORE-2610 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta14 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017