January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2136) Using management CLI with client configuration still prompts for username/password

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2136?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2136: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Using management CLI with client configuration still prompts for username/password > ---------------------------------------------------------------------------------- > > Key: WFCORE-2136 > URL: https://issues.jboss.org/browse/WFCORE-2136 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Security > Reporter: Zach Rhoads > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha19 > > > When configuring the wildfly management cli to use an elytron client config file, server still prompts for username password. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2115) Upgrade jboss-remoting to 5.0.0.Beta13

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2115?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2115: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Upgrade jboss-remoting to 5.0.0.Beta13 > -------------------------------------- > > Key: WFCORE-2115 > URL: https://issues.jboss.org/browse/WFCORE-2115 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 3.0.0.Alpha15 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Fix For: 3.0.0.Alpha19 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2177) Remove the 'elytron' supplement from the Remoting subsystem.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2177?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2177: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Remove the 'elytron' supplement from the Remoting subsystem. > ------------------------------------------------------------ > > Key: WFCORE-2177 > URL: https://issues.jboss.org/browse/WFCORE-2177 > Project: WildFly Core > Issue Type: Task > Components: Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha19 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2163) Server does not start when Elytron authentication + legacy SSL is used in HTTP management interface

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2163?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2163: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Server does not start when Elytron authentication + legacy SSL is used in HTTP management interface > --------------------------------------------------------------------------------------------------- > > Key: WFCORE-2163 > URL: https://issues.jboss.org/browse/WFCORE-2163 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Alpha19 > > > In case when legacy security-realm for SSL is used together with Elytron authentication in HTTP management interface then server is not started. > I am using following configuration for HTTP management interface (see Steps to Reproduce for more details): > {code} > <http-interface http-authentication-factory="management-http-authentication" security-realm="ManagementRealmHTTPS"> > <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/> > <socket-binding http="management-http" https="management-https"/> > </http-interface> > {code} > Server is not started and following errors occur in log: > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: WFLYSRV0083: Failed to start the http-interface service > at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:330) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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) > Caused by: java.lang.IllegalStateException: WFLYDMHTTP0015: No SecurityRealm or SSLContext has been provided. > at org.jboss.as.domain.http.server.ManagementHttpServer.getSSLContext(ManagementHttpServer.java:225) > at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:254) > at org.jboss.as.domain.http.server.ManagementHttpServer.access$2400(ManagementHttpServer.java:107) > at org.jboss.as.domain.http.server.ManagementHttpServer$Builder.build(ManagementHttpServer.java:589) > at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:292) > ... 5 more > {code} > and > {code} > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]) - failure description: { > "WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: WFLYSRV0083: Failed to start the http-interface service > Caused by: java.lang.IllegalStateException: WFLYDMHTTP0015: No SecurityRealm or SSLContext has been provided."}, > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.management.http.extensible"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]) - failure description: { > "WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: WFLYSRV0083: Failed to start the http-interface service > Caused by: java.lang.IllegalStateException: WFLYDMHTTP0015: No SecurityRealm or SSLContext has been provided."}, > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.management.http.extensible"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > {code} > According to comments in EAP7-545 Analysis document [1], when security-realm and http-authentication-factory are specified but no ssl-context is used then it should lead to use legacy security-realm for SSL configuration and http-authentication-factory for authentication. > [1] https://docs.google.com/document/d/1LsS-CGUJSDwGcFUva0g-BF9ZIq0jwx__1e_oJ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2155) Update <remote /> Domain Controller to reference an AuthenticationContext

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2155?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2155: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Update <remote /> Domain Controller to reference an AuthenticationContext > ------------------------------------------------------------------------- > > Key: WFCORE-2155 > URL: https://issues.jboss.org/browse/WFCORE-2155 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha19 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2168) Remove CredentialStoreClient in favour of CredentialSource

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2168?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2168: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Remove CredentialStoreClient in favour of CredentialSource > ---------------------------------------------------------- > > Key: WFCORE-2168 > URL: https://issues.jboss.org/browse/WFCORE-2168 > Project: WildFly Core > Issue Type: Task > Components: Security > Affects Versions: 3.0.0.Alpha16 > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: 3.0.0.Alpha19 > > > With recent changes to Elytron Authentication Client make credential referencing use CredentialSource instead of CredentialStoreClient. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2191) Upgrade to WildFly Elytron 1.1.0.Beta19

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2191?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2191: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Upgrade to WildFly Elytron 1.1.0.Beta19 > --------------------------------------- > > Key: WFCORE-2191 > URL: https://issues.jboss.org/browse/WFCORE-2191 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha19 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2190) Realm implementations need to implement getRealmIdentityPrincipal on the realm identities.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2190?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2190: ------------------------------- Fix Version/s: 3.0.0.Alpha19 (was: 3.0.0.Alpha18) > Realm implementations need to implement getRealmIdentityPrincipal on the realm identities. > ------------------------------------------------------------------------------------------ > > Key: WFCORE-2190 > URL: https://issues.jboss.org/browse/WFCORE-2190 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha19 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-421) cli tab-completion: filtering out operations not applicable to a resource

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-421?page=com.atlassian.jira.plugin... ] Jean-Francois Denise closed WFCORE-421. --------------------------------------- Resolution: Won't Fix The management model doesn't expose what are the operations one could call on non existing / existing resources. As said in previous comment, "*" can be used instead of bogus name. > cli tab-completion: filtering out operations not applicable to a resource > ------------------------------------------------------------------------- > > Key: WFCORE-421 > URL: https://issues.jboss.org/browse/WFCORE-421 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Environment: JBoss AS 7.0.1 > Reporter: Bill Meyer > Assignee: Jean-Francois Denise > Priority: Minor > > In this example, no Data Sources already exist (clean config). > If I enter the following into the CLI and hit <tab>: > /subsystem=datasources/data-source=:<tab> > I get no operation hints. If I use a bogus resource name that doesn't exist and hit <tab>: > [standalone@localhost:9999 /] /subsystem=datasources/data-source=DoesNotExistDS:<tab> > add disable enable flush-all-connection-in-pool > flush-idle-connection-in-pool read-attribute read-children-names read-children-resources > read-children-types read-operation-description read-operation-names read-resource > read-resource-description remove test-connection-in-pool validate-address > write-attribute > I get all the operations available. This should be made more consistent. The preference, IMO, would be to not have to specify a bogus name and still get the operations list: > [standalone@localhost:9999 /] /subsystem=datasources/data-source=:<tab> > or simpler yet: > [standalone@localhost:9999 /] /subsystem=datasources/data-source:<tab> > (no empty equal sign). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2196) Copy ClientCompatibilityUnitTestCase into core from full

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-2196: ---------------------------------- Summary: Copy ClientCompatibilityUnitTestCase into core from full Key: WFCORE-2196 URL: https://issues.jboss.org/browse/WFCORE-2196 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Kabir Khan Assignee: Brian Stansberry [3:44 PM] Kabir Khan: @DarranLofthouse I see this in the logs [3:44 PM] Kabir Khan: 2017-01-16 15:38:55,589 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.security.security-realm.ManagementRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ManagementRealm: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1919) 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) Caused by: java.lang.NoSuchMethodError: org.wildfly.security.auth.realm.LegacyPropertiesSecurityRealm$Builder.setDefaultRealm(Ljava/lang/String;)Lorg/wildfly/security/auth/realm/LegacyPropertiesSecurityRealm$Builder; at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:187) at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:171) at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) ... 3 more [3:44 PM] Kabir Khan: @BrianStansberry perhaps ClientCompatibilityUnitTestCase should be in core rather than full? [3:47 PM] Darran Lofthouse: @KabirKhan do we have any error as to why it is not up? [3:47 PM] Kabir Khan: Yes, the NoSuchErrorException [3:48 PM] Kabir Khan: umm :) [3:48 PM] Kabir Khan: I invented a new class [3:48 PM] Kabir Khan: NoSuchMethodError [3:48 PM] Kabir Khan: I pasted it above my mention of Brian [3:49 PM] Kabir Khan: So PropertiesRealmDefinition is calling a non-existent setDefaultRealm() method on LegacyPropertiesSecurityRealm's builder [3:49 PM] Darran Lofthouse: @KabirKhan if the method doesn't exist that means the wrong Elytron version is being used [3:50 PM] Kabir Khan: Argh [3:50 PM] Kabir Khan: I released core without your PR merged [3:50 PM] Darran Lofthouse: LOL - that would explain how the wrong Elytron version is being used ;-) [3:51 PM] Kabir Khan: ok, I'll try again [3:53 PM] Brian Stansberry: @KabirKhan perhaps but I bet there was a reason we didn't move it [3:55 PM] Kabir Khan: On the positive side, it is not the night before the release [3:58 PM] Brian Stansberry: @KabirKhan if there is such a reason I don't see it in the code for that test [3:58 PM] Kabir Khan: yeah, me neither [3:59 PM] Kabir Khan: @BrianStansberry I'll rerelease core to fix my previous error [3:59 PM] Kabir Khan: but can look into this [3:59 PM] Kabir Khan: I'll create a Jira so I remember [3:59 PM] Brian Stansberry: @KabirKhan thanks [4:00 PM] Kabir Khan: although, I guess in this case it was a good thing [4:00 PM] Brian Stansberry: @KabirKhan tangent: do you recall if in the mixed domain tests we have the test driver invoke any ops against the legacy slave? [4:00 PM] Kabir Khan: this was what alerted e to the problem [4:00 PM] Kabir Khan: @BrianStansberry not off the top of my head, but I'd guess there should be at least some direct read-resource calls [4:00 PM] Brian Stansberry: @KabirKhan ah, you mean it was something in the full config that failed, that wouldn't be in core? [4:01 PM] Brian Stansberry: i'd say we shouldn't move that test but instead copy it [4:01 PM] Kabir Khan: @BrianStansberry there was an update to the elytron subsystem in full calling some stuff in Elytron [4:02 PM] Kabir Khan: that Elytron stuff wasn't there, because I had forgotten to merge the core PR that brought it in the Elytron upgrade [4:02 PM] Kabir Khan: so I saw NoSuchMethodErrors -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 January 2017