May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2016) Change sasl-authentication-factor for management auth works after reload, but not after server restart

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2016?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2016: ------------------------------------- Fix Version/s: 3.0.0.Beta23 (was: 3.0.0.Beta22) > Change sasl-authentication-factor for management auth works after reload, but not after server restart > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-2016 > URL: https://issues.jboss.org/browse/WFCORE-2016 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Zach Rhoads > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta23 > > > I can successfully configure a new sasl-authentication-factory and assign it to the management interface: > {code} > /subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add() > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:set-password(clear={password="password123"}) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add-attribute(name=Roles, value=["Admin","Guest"]) > /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles) > /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper) > /subsystem=elytron/sasl-authentication-factory=example-sasl-auth:add(sasl-server-factory=configured,security-domain=exampleFsSD,mechanism-configurations=[{mechanism-name=DIGEST-MD5,mechanism-realm-configurations=[{realm-name=exampleSaslRealm}]}]) > /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=example-sasl-auth) > reload > {code} > after reload, i am forced to re-authenticate and it succeeds: > {code} > [standalone@localhost:9990 /] reload > Authenticating against security realm: exampleSaslRealm > Username: user1 > Password: > [standalone@localhost:9990 /] > {code} > Once i restart the server though and try to connect, i get a timeout: > {code} > $ ./jboss-cli.sh -c > Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out > {code} > It also fails if i force no local auth: > {code} > $ ./jboss-cli.sh -c --no-local-auth > Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out > {code}/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2609) CLIRolloutPlanTestCase hang

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2609?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2609: ------------------------------------- Fix Version/s: 3.0.0.Beta23 (was: 3.0.0.Beta22) > 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.Beta23 > > Attachments: WFCORE-2609_threads.txt > > > Hang: > https://ci.wildfly.org/viewLog.html?buildId=53176&buildTypeId=WF_MasterWi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2589?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2589: ------------------------------------- Fix Version/s: 3.0.0.Beta23 (was: 3.0.0.Beta22) > 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.Beta23 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2528?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2528: ------------------------------------- Fix Version/s: 3.0.0.Beta23 (was: 3.0.0.Beta22) > 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.Beta23 > > > Leftover cleanup from WFCORE-1958 since VaultPasswordsInCLITestCase is not enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-125) Move from testng to JUnit

by James Perkins (JIRA)

James Perkins created LOGTOOL-125: ------------------------------------- Summary: Move from testng to JUnit Key: LOGTOOL-125 URL: https://issues.jboss.org/browse/LOGTOOL-125 Project: Log Tool Issue Type: Task Reporter: James Perkins Most JBoss projects use JUnit over testng. Test assertions are done in reverse order which, for me at least, causes confusion when adding new tests. This project should move to using JUnit to avoid confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2835) Upgrade PicketBox to 5.0.2.Final

by Stefan Guilhen (JIRA)

Stefan Guilhen created WFCORE-2835: -------------------------------------- Summary: Upgrade PicketBox to 5.0.2.Final Key: WFCORE-2835 URL: https://issues.jboss.org/browse/WFCORE-2835 Project: WildFly Core Issue Type: Component Upgrade Components: Security Affects Versions: 3.0.0.Beta21 Reporter: Stefan Guilhen Assignee: Stefan Guilhen -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-972) Release PicketBox 5.0.2.Final

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-972?page=com.atlassian.jira.plug... ] Stefan Guilhen closed SECURITY-972. ----------------------------------- Resolution: Done PicketBox 5.0.2.Final has been released and is available on Nexus. > Release PicketBox 5.0.2.Final > ----------------------------- > > Key: SECURITY-972 > URL: https://issues.jboss.org/browse/SECURITY-972 > Project: PicketBox > Issue Type: Task > Components: JBossSX, Security-SPI > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-972) Release PicketBox 5.0.2.Final

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-972?page=com.atlassian.jira.plug... ] Stefan Guilhen updated SECURITY-972: ------------------------------------ Component/s: JBossSX, Security-SPI > Release PicketBox 5.0.2.Final > ----------------------------- > > Key: SECURITY-972 > URL: https://issues.jboss.org/browse/SECURITY-972 > Project: PicketBox > Issue Type: Task > Components: JBossSX, Security-SPI > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-971) SecurityKeyManager should use delegate for methods inherited from X509ExtendedKeyManager when possible

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-971?page=com.atlassian.jira.plug... ] Stefan Guilhen updated SECURITY-971: ------------------------------------ Git Pull Request: https://github.com/picketbox/picketbox/pull/69 > SecurityKeyManager should use delegate for methods inherited from X509ExtendedKeyManager when possible > ------------------------------------------------------------------------------------------------------ > > Key: SECURITY-971 > URL: https://issues.jboss.org/browse/SECURITY-971 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: PicketBox_5_0_1.Final > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > Fix For: PicketBox_5_0_2.Final > > > SecurityKeyManager now extends X509ExtendedKeyManager but the methods inherited from this class have been left unimplemented (i.e. return null). > The implementation should check if the delegate instance is of type X509ExtendedKeyManager and use the delegate for these methods instead of relying on the default implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-971) SecurityKeyManager should use delegate for methods inherited from X509ExtendedKeyManager when possible

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-971?page=com.atlassian.jira.plug... ] Stefan Guilhen resolved SECURITY-971. ------------------------------------- Resolution: Done > SecurityKeyManager should use delegate for methods inherited from X509ExtendedKeyManager when possible > ------------------------------------------------------------------------------------------------------ > > Key: SECURITY-971 > URL: https://issues.jboss.org/browse/SECURITY-971 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: PicketBox_5_0_1.Final > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > Fix For: PicketBox_5_0_2.Final > > > SecurityKeyManager now extends X509ExtendedKeyManager but the methods inherited from this class have been left unimplemented (i.e. return null). > The implementation should check if the delegate instance is of type X509ExtendedKeyManager and use the delegate for these methods instead of relying on the default implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017