September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7194: ---------------------------------- No, to use JVM default it will have to be defined explicitly. The idea is to not abet administrators to use non-JVM-portable configuration. Sorry. > Simplify creation of trust/key-manager in elytron > ------------------------------------------------- > > Key: WFLY-7194 > URL: https://issues.jboss.org/browse/WFLY-7194 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > > If I want to setup TLS [1], I have to create key manager with CLI command > {code} > /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509") > {code} > 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used. > 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone. > 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required. > {code} > <xs:attribute name="key-store" type="xs:string" use="optional"> > <xs:annotation> > <xs:documentation> > Reference to the KeyStore to use with the KeyManager. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} > 4.{{password}} attribute is optional, probably should be required > {code} > "password" => { > "type" => STRING, > "description" => "The password to use when initialising the underlying KeyManagerFactory.", > "expressions-allowed" => true, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "1.0.0", > "reason" => "Will be updated to use proper CredentialStore references." > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7149) Unable to remove elytron subsystem with defined properties-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7149?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-7149: -------------------------------- Assignee: Bartosz Baranowski (was: Jan Kalina) > Unable to remove elytron subsystem with defined properties-realm > ---------------------------------------------------------------- > > Key: WFLY-7149 > URL: https://issues.jboss.org/browse/WFLY-7149 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Radim Hatlapatka > Assignee: Bartosz Baranowski > Priority: Critical > > When having elytron subsystem with only defined property-realm and calling remove on the subsystem, it fails due unsatisfied dependencies \[1\]. The subsystem is created from scratch with no dependencies outside of the subsystem => it shouldn't fail to remove. > \[1\] > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron:remove > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service elytron.security-properties was depended upon by service org.wildfly.security.security-realm.elytron-security > Service elytron.core-service was depended upon by service org.wildfly.security.security-realm.elytron-security", > "rolled-back" => true > } > {noformat} -- 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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7192?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-7192: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1365939 Bugzilla Update: Perform > '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] (DROOLS-1304) OOPath ReactiveList remove cases

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1304: ----------------------------------- Summary: OOPath ReactiveList remove cases Key: DROOLS-1304 URL: https://issues.jboss.org/browse/DROOLS-1304 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] (SECURITY-958) JASPIC implementation in JBoss EAP 7.0.0 seems to contradict the javadoc of the ServerAuthModule interface

by Enrique González Martínez (JIRA)

Enrique González Martínez created SECURITY-958: -------------------------------------------------- Summary: JASPIC implementation in JBoss EAP 7.0.0 seems to contradict the javadoc of the ServerAuthModule interface Key: SECURITY-958 URL: https://issues.jboss.org/browse/SECURITY-958 Project: PicketBox Issue Type: Bug Reporter: Enrique González Martínez Assignee: Enrique González Martínez The EAP 7.0.0 JASPIC ServerAuthModule framework passes the request policy and response policy objects as null into the initialize() method. The spec and java docs say that both must not be null. http://docs.oracle.com/javaee/6/api/javax/security/auth/message/module/Se... https://docs.oracle.com/javaee/7/api/javax/security/auth/message/module/S... The javadoc and spec says: "The request policy and the response policy must not both be null". Wildfly 10.0.0.Final has the same issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFLY-7194: ------------------------------------ Does that mean "Default" will be declared as default value in model? So if I don't specify algorithm "Default" will be applied? [~dlofthouse] [~honza889] My motivation for point 1 is part of general idea: "Provide a possibility to create SSL Context in simple way." That's why I think in terms, "does that really need to be provided by user"? I really like that user can configure pretty everything now, but I think also on people who want ideally specify just keystore and password to make TLS work. > Simplify creation of trust/key-manager in elytron > ------------------------------------------------- > > Key: WFLY-7194 > URL: https://issues.jboss.org/browse/WFLY-7194 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > > If I want to setup TLS [1], I have to create key manager with CLI command > {code} > /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509") > {code} > 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used. > 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone. > 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required. > {code} > <xs:attribute name="key-store" type="xs:string" use="optional"> > <xs:annotation> > <xs:documentation> > Reference to the KeyStore to use with the KeyManager. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} > 4.{{password}} attribute is optional, probably should be required > {code} > "password" => { > "type" => STRING, > "description" => "The password to use when initialising the underlying KeyManagerFactory.", > "expressions-allowed" => true, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "1.0.0", > "reason" => "Will be updated to use proper CredentialStore references." > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7201) Statement.cancel() is not invoked until the statement is completed

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-7201?page=com.atlassian.jira.plugin.... ] Lin Gao deleted WFLY-7201: -------------------------- > Statement.cancel() is not invoked until the statement is completed > ------------------------------------------------------------------ > > Key: WFLY-7201 > URL: https://issues.jboss.org/browse/WFLY-7201 > Project: WildFly > Issue Type: Bug > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > > Hi, > in our application we are using the {{Statement.cancel()}} method to stop long-running queries; in Wildfly 9.0.2 this is not working because the {{cancel()}} method is synchronized using a lock which is not released until the query is executed. In {{WrappedStatement}}: > {code:java} > public void cancel() throws SQLException > { > if (doLocking) > lock(); > try > { > /* ... */ > {code} > It seems this behaviour has changed from version 1.2.5.Final of ironjacamar-jdbc; in version 1.2.4.Final {{WrappedStatement.cancel}} doesn't try to obtain the lock. > Probably I'm missing something, but to me it's strange that in order to cancel a statement you have to wait for its completion. > Thank you, > lorenzo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7201) Statement.cancel() is not invoked until the statement is completed

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-7201?page=com.atlassian.jira.plugin.... ] Lin Gao moved JBEAP-6173 to WFLY-7201: -------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7201 (was: JBEAP-6173) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) Affects Version/s: (was: 7.0.0.GA) > Statement.cancel() is not invoked until the statement is completed > ------------------------------------------------------------------ > > Key: WFLY-7201 > URL: https://issues.jboss.org/browse/WFLY-7201 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > > Hi, > in our application we are using the {{Statement.cancel()}} method to stop long-running queries; in Wildfly 9.0.2 this is not working because the {{cancel()}} method is synchronized using a lock which is not released until the query is executed. In {{WrappedStatement}}: > {code:java} > public void cancel() throws SQLException > { > if (doLocking) > lock(); > try > { > /* ... */ > {code} > It seems this behaviour has changed from version 1.2.5.Final of ironjacamar-jdbc; in version 1.2.4.Final {{WrappedStatement.cancel}} doesn't try to obtain the lock. > Probably I'm missing something, but to me it's strange that in order to cancel a statement you have to wait for its completion. > Thank you, > lorenzo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7200) Websocket compression should be controlled through the management model

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-7200: ------------------------------------ Summary: Websocket compression should be controlled through the management model Key: WFLY-7200 URL: https://issues.jboss.org/browse/WFLY-7200 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7199) Websocket compression should be controlled through the management model

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-7199: ------------------------------------ Summary: Websocket compression should be controlled through the management model Key: WFLY-7199 URL: https://issues.jboss.org/browse/WFLY-7199 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- 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