September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-638) Add support for hashed usernames.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-638?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-638: --------------------------------- Component/s: HTTP > Add support for hashed usernames. > --------------------------------- > > Key: ELY-638 > URL: https://issues.jboss.org/browse/ELY-638 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, HTTP > Reporter: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > The latest HTTP Digest RFC https://datatracker.ietf.org/doc/rfc7616/ adds support for hashed usernames. > https://tools.ietf.org/html/rfc7616#page-12 > Passing in this hash within the name field of IdentityLocator may be suitable for a realm to map - alternatively NameRewriters and RealmMappers may be needed to handle some of this, or IdentityLocator could be extended to add fields for hashed username and algorithm. Or other options. > Have scheduled for Elytron 2 as this is a new optional part of the RFC. It may turn out to be a feature of a mech never used but general support for an alternative form of a username like this sounds reasonable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1302) OOPath ReactiveList remove cases

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1302: -------------------------------------- Summary: OOPath ReactiveList remove cases Key: DROOLS-1302 URL: https://issues.jboss.org/browse/DROOLS-1302 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.CR2 Reporter: Matteo Mortari Assignee: Matteo Mortari Priority: Minor * Removing element from ReactiveList is not covered * Ensure removing from 1 out of many ReactiveList does affect only the relevant lists when issuing modification to a ReactiveObject -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5499) Channel end notification received, closing channel ... should be logged at debug in EjbLogger

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5499?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5499: ----------------------------------------------- Vlado Pakan <vpakan(a)redhat.com> changed the Status of [bug 1271538|https://bugzilla.redhat.com/show_bug.cgi?id=1271538] from POST to MODIFIED > Channel end notification received, closing channel ... should be logged at debug in EjbLogger > --------------------------------------------------------------------------------------------- > > Key: WFLY-5499 > URL: https://issues.jboss.org/browse/WFLY-5499 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Reporter: Takayuki Konishi > > Remote naming is logging this at ERROR, though it seems normal and no adverse effects are apparent, we should log it at debug instead of error. > {code} > ERROR [org.jboss.as.ejb3] (Remoting "master@ap02:server-apip" task-2) JBAS014141: Channel end notification received, closing channel Channel ID 6b8f00d7 (inbound) of Remoting connection 36e4f81b to /192.168.1.10:64354 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1730) Singleton service is not correctly being set in WILDFLY

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1730?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1730: ------------------------------------------------- Vlado Pakan <vpakan(a)redhat.com> changed the Status of [bug 1367793|https://bugzilla.redhat.com/show_bug.cgi?id=1367793] from POST to MODIFIED > Singleton service is not correctly being set in WILDFLY > ------------------------------------------------------- > > Key: WFCORE-1730 > URL: https://issues.jboss.org/browse/WFCORE-1730 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 3.0.0.Alpha5 > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > WILDFLY doesn't call ServiceLoader (META-INF/services/org.jboss.msc.service.ServiceActivator) when it is deployed in EAR/lib. The SingletonService (not a singleton EJB) is activated in the ServiceLoader so the SingletonService hasn't been activated from the first. It works as expected when deployed as an EJB (not in EAR/lib). > When the ServiceLoader is called, a message of "HATimerService will be installed!" is logged and the SingletonService will be activated. > $ fgrep -e HATimerService -e '[org.jboss.as.clustering.singleton]' domain/servers/server-one/log/server.log > 12:14:52,373 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator] (MSC service thread 1-7) HATimerService will be installed! > 12:14:56,251 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 54) JBAS010342: master:server-one/singleton elected as the singleton provider of the jboss.quickstart.ha.singleton.timer service > 12:14:56,251 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 54) JBAS010340: This node will now operate as the singleton provider of the jboss.quickstart.ha.singleton.timer service > 12:14:56,268 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerService] (MSC service thread 1-8) Start HASingleton timer service 'org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATim > erService' > 12:14:56,873 INFO [org.jboss.as.clustering.singleton] (notification-thread-0) JBAS010342: master:server-one/singleton elected as the singleton provider of the jboss.quickstart.ha.singleton.timer service -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3639) default-web-module doesn't work for non default hosts & servers

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3639?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3639: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/8953 (was: https://github.com/wildfly/wildfly/pull/8422) > default-web-module doesn't work for non default hosts & servers > --------------------------------------------------------------- > > Key: WFLY-3639 > URL: https://issues.jboss.org/browse/WFLY-3639 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > If you use config like this: > {code:xml} > <host name="default-host" default-web-module="myapp1.war" alias="webapp.domain1.com"/> > <host name="other-host" default-web-module="myapp2.war" alias="test.domain2.net"/> > {code} > and have apps myapp1.war & myapp2.war deployed myappwar2.war won't be bind to other-host. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1814) Move to woodstox 5.x

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-1814: ----------------------------------- Summary: Move to woodstox 5.x Key: WFCORE-1814 URL: https://issues.jboss.org/browse/WFCORE-1814 Project: WildFly Core Issue Type: Task Components: XML Frameworks Affects Versions: 3.0.0.Alpha8 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Woodstox has moved to new home and is now better maintained. https://github.com/FasterXML/woodstox Version 5.0.1 was the first build from new repo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7192) 'name' attribute missing in XSD while required by web subsystem parser

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFLY-7192?page=com.atlassian.jira.plugin.... ] Peter Palaga moved JBEAP-6153 to WFLY-7192: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7192 (was: JBEAP-6153) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: (was: Web (JBoss Web)) > 'name' attribute missing in XSD while required by web subsystem parser > ---------------------------------------------------------------------- > > Key: WFLY-7192 > URL: https://issues.jboss.org/browse/WFLY-7192 > Project: WildFly > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > Labels: downstream_dependency > > Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1365939 , originaly reported by [~paramjindal] > While configuring the global valve using the following article : > https://access.redhat.com/solutions/379813 > It is mandatory that the "name" attribute of valve must match the "auth-method" that is specified in the "WEB-INF/web.xml". > So "name" attribute is mandatory to configure this valve. > but it is not mentioned in the schema of valve as shown below : > {code:xml} > <xs:element name="valve"> > <xs:complexType> > <xs:sequence> > <xs:element name="param" minOccurs="0" maxOccurs="unbounded" type="paramType" /> > </xs:sequence> > <xs:attribute name="class-name" type="xs:string" use="required" /> > <xs:attribute name="module" type="xs:string" use="required" /> > <xs:attribute name="enabled" default="true" type="xs:boolean" /> > </xs:complexType> > </xs:element> > {code} > Version-Release number of selected component (if applicable): -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-631: -------------------------------------- [~honza889] Could you please take a look into this one? Should be a small fix. > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: ELY-631 > URL: https://issues.jboss.org/browse/ELY-631 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta9 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-631: ------------------------------------ Assignee: Jan Kalina (was: Darran Lofthouse) > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: ELY-631 > URL: https://issues.jboss.org/browse/ELY-631 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta9 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7191) alias-filter of filtering-key-store should be required in model

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7191?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-7191: ------------------------------- Description: {{alias-filter}} attribute of filtering-key-store should be required in model Elytron doesn't allow null value of {{alias-filter}} attribute of resource filtering-key-store. If I try to create filtering-key-store withou alias-filter I get: {code} [standalone@localhost:9990 /] /subsystem=elytron/filtering-key-store=fks:add(key-store=server) { "outcome" => "failed", "failure-description" => { "WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.fks" => "org.jboss.msc.service.StartException in service org.wildfly.security.key-store.fks: java.lang.IllegalArgumentException: Parameter 'filterString' may not be null Caused by: java.lang.IllegalArgumentException: Parameter 'filterString' may not be null"}, "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.key-store.fks"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined }, "rolled-back" => true } {code} So, {{alias-filter}} can be also defined in model as required, it means {{"nillable" => false}}. Now it is: {code} "alias-filter" => { "type" => STRING, "description" => "A filter to apply to the aliases returned from the KeyStore, can either be a comma separated list of aliases to return or one of the following formats ALL:-alias1:-alias2, NONE:+alias1:+alias2", "expressions-allowed" => true, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "resource-services" }, {code} was: alias-filter of filtering-key-store should be required in model Elytron doesn't allow null value of {{alias-filter}} attribute of resource filtering-key-store. If I try to create filtering-key-store withou alias-filter I get: {code} [standalone@localhost:9990 /] /subsystem=elytron/filtering-key-store=fks:add(key-store=server) { "outcome" => "failed", "failure-description" => { "WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.fks" => "org.jboss.msc.service.StartException in service org.wildfly.security.key-store.fks: java.lang.IllegalArgumentException: Parameter 'filterString' may not be null Caused by: java.lang.IllegalArgumentException: Parameter 'filterString' may not be null"}, "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.key-store.fks"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined }, "rolled-back" => true } {code} So, {{alias-filter}} can be also defined in model as required, it means {{"nillable" => false}}. Now it is: {code} "alias-filter" => { "type" => STRING, "description" => "A filter to apply to the aliases returned from the KeyStore, can either be a comma separated list of aliases to return or one of the following formats ALL:-alias1:-alias2, NONE:+alias1:+alias2", "expressions-allowed" => true, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "resource-services" }, {code} > alias-filter of filtering-key-store should be required in model > --------------------------------------------------------------- > > Key: WFLY-7191 > URL: https://issues.jboss.org/browse/WFLY-7191 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Optional > > {{alias-filter}} attribute of filtering-key-store should be required in model > Elytron doesn't allow null value of {{alias-filter}} attribute of resource filtering-key-store. If I try to create filtering-key-store withou alias-filter I get: > {code} > [standalone@localhost:9990 /] /subsystem=elytron/filtering-key-store=fks:add(key-store=server) > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.fks" => "org.jboss.msc.service.StartException in service org.wildfly.security.key-store.fks: java.lang.IllegalArgumentException: Parameter 'filterString' may not be null > Caused by: java.lang.IllegalArgumentException: Parameter 'filterString' may not be null"}, > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.key-store.fks"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > }, > "rolled-back" => true > } > {code} > So, {{alias-filter}} can be also defined in model as required, it means {{"nillable" => false}}. Now it is: > {code} > "alias-filter" => { > "type" => STRING, > "description" => "A filter to apply to the aliases returned from the KeyStore, can either be a comma separated list of aliases to return or one of the following formats ALL:-alias1:-alias2, NONE:+alias1:+alias2", > "expressions-allowed" => true, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016