May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8773) Update EjbClientContextSetupProcessor.RegistrationService#transformOne to make use of the SSLContext from the RemoteOutboundConnectionService

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8773?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8773: ----------------------------------- Fix Version/s: 11.0.0.Beta1 > Update EjbClientContextSetupProcessor.RegistrationService#transformOne to make use of the SSLContext from the RemoteOutboundConnectionService > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8773 > URL: https://issues.jboss.org/browse/WFLY-8773 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8772) Deployments referencing outbound connection with authentication context always use Elytron default-authentication-context

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8772?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8772: ----------------------------------- Fix Version/s: 11.0.0.Beta1 > Deployments referencing outbound connection with authentication context always use Elytron default-authentication-context > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8772 > URL: https://issues.jboss.org/browse/WFLY-8772 > Project: WildFly > Issue Type: Bug > Components: Remoting, Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Labels: eap7.1-rfe-blocker, eap7.1-rfe-failure, eap71_beta_candidate > Fix For: 11.0.0.Beta1 > > > Analysis document for EAP7-551 states the following: > {quote}This RFE is to add a reference to the new authentication-context capability to the remote-outbound-connection resource and make use of it satisfy the security requirements for the outbound connections being established. > The AuthenticationContext will be used to access both information required for authentication and also for any SSLContext required for the connection. > A newly referenced authentication-context will be used to provide all security configuration for outbound connections.{quote} > However, currently the remoting outbound connections will only use Elytron default authentication context and ignore authentication context defined in remoting outbound connection resource: > * If no default authentication context is defined in Elytron subsystem but remote outbound connection has defined one, no authentication context is associated with remote outbound connection. > * If the default authentication context is defined in Elytron subsystem but no authentication context is defined in remote outbound connection, remoting assumes that outbound connection uses legacy security. > * If the default authentication context is defined in Elytron subsystem and different authentication context is defined in remote outbound connection, the remote outbound connection will use the Elytron subsystem default none the less. > * The authentication context defined in outbound remote connection will only work if it is the same as default authentication context in Elytron subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2774) Move org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase to wildfly-core

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2774?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2774: ------------------------------------- Fix Version/s: 3.0.0.Beta22 > Move org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase to wildfly-core > ------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2774 > URL: https://issues.jboss.org/browse/WFCORE-2774 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security, Test Suite > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Beta22 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2671) CLI Opertation 'load' for Elytron key-store does not correctly re-read keystore

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2671?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2671: ------------------------------------- Fix Version/s: 3.0.0.Beta22 > CLI Opertation 'load' for Elytron key-store does not correctly re-read keystore > ------------------------------------------------------------------------------- > > Key: WFCORE-2671 > URL: https://issues.jboss.org/browse/WFCORE-2671 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta21 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Blocker > Fix For: 3.0.0.Beta22 > > > When keystore (or cerficate in keystore) is changed during server runtime then CLI opertation {{load}} can be used for {{/subsystem=elytron/key-store=...}} to re-reading this keystore in server. However after calling this operation server still works with original keystore/certificate. Then CLI reads current keystore correctly, but in case when ssl-context which uses that key-store is used then original keystore is still used by server. Reload of server is required to correctly re-read the new keystore. See Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2814) There is description of "case-sensitive" attribute inconsistency between model and XSD.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2814?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2814: ------------------------------------- Fix Version/s: 3.0.0.Beta22 > There is description of "case-sensitive" attribute inconsistency between model and XSD. > --------------------------------------------------------------------------------------- > > Key: WFCORE-2814 > URL: https://issues.jboss.org/browse/WFCORE-2814 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Ilia Vassilev > Fix For: 3.0.0.Beta22 > > > There is description of "case-sensitive" attribute inconsistency between model and XSD. > In XSD is missing default value. > Please add to XSD default value and unify description. > I suggest use description from model as right one: "Case sensitivity of the credential store. If case insensitive only lower case names are allowed for aliases.". > *MODEL* > {code} > "case-sensitive" => { > "type" => BOOLEAN, > "description" => "Case sensitivity of the credential store. If case insensitive only lower case names are allowed for aliases.", > "attribute-group" => "implementation", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > *DMR* > {code} > <xs:attribute name="case-sensitive" type="xs:boolean" use="optional"> > <xs:annotation> > <xs:documentation> > Indicates that the credential store is case sensitive and should then allow for upper case in alias. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2808) The Remote Outbound Connection does not use an SSLContext from the injected SecurityRealm or AuthenticationContext

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2808?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2808: ------------------------------------- Fix Version/s: 3.0.0.Beta22 > The Remote Outbound Connection does not use an SSLContext from the injected SecurityRealm or AuthenticationContext > ------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-2808 > URL: https://issues.jboss.org/browse/WFCORE-2808 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Fix For: 3.0.0.Beta22 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2777) Elytron credential-store should offer operations instead of alias resource

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2777?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2777: ------------------------------------- Fix Version/s: 3.0.0.Beta22 > Elytron credential-store should offer operations instead of alias resource > -------------------------------------------------------------------------- > > Key: WFCORE-2777 > URL: https://issues.jboss.org/browse/WFCORE-2777 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta18 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Fix For: 3.0.0.Beta22 > > > Elytron credential-store resources should offer operations instead of alias resource, as for key-stores, as it can be based on any key-store too. > The reason is more described in WFCORE-2691 or related mailing thread on wildfly-dev. > Setting priority to blocker by WFCORE-2691 and WFCORE-2737. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2809) Fix parsing and handling of the legacy username attribute for a remote-outbound-connection

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2809?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2809: ------------------------------------- Fix Version/s: 3.0.0.Beta22 > Fix parsing and handling of the legacy username attribute for a remote-outbound-connection > ------------------------------------------------------------------------------------------ > > Key: WFCORE-2809 > URL: https://issues.jboss.org/browse/WFCORE-2809 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Fix For: 3.0.0.Beta22 > > > Currently, when the username attribute is not specified for a remote-outbound-connection (i.e., for the Elytron remote-outbound-connection case), the username is erroneously being treated as the string “undefined”. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2804) Elytron key-managers: operations do not reflect alias-filter attribute

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2804?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2804: ------------------------------------- Fix Version/s: 3.0.0.Beta22 > Elytron key-managers: operations do not reflect alias-filter attribute > ---------------------------------------------------------------------- > > Key: WFCORE-2804 > URL: https://issues.jboss.org/browse/WFCORE-2804 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta21 > Reporter: Ondrej Kotek > Assignee: Michal Petrov > Fix For: 3.0.0.Beta22 > > > Operations {{add}} and {{write-attribute}} of Elytron {{key-managers}} do not reflect {{alias-filter}} attribute, see steps to reproduce. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1567) Threads in BLOCKED state in ProjectClassLoader and ParseTools

by Arkady Syamtomov (JIRA)

Arkady Syamtomov created DROOLS-1567: ---------------------------------------- Summary: Threads in BLOCKED state in ProjectClassLoader and ParseTools Key: DROOLS-1567 URL: https://issues.jboss.org/browse/DROOLS-1567 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.Final Reporter: Arkady Syamtomov Assignee: Mario Fusco Building the knowledge bases in parallel threads does not scale due to the recurrent synchronised call of Class.forName, detected in ProjectClassLoader and org.mvel2.util.ParceTools. While in the org.drools.core.common.ProjectClassLoader the classes, if not found, are blacklisted, in the org.mvel2.util.ParceTools there is no blacklist logic implemented at all. Nevertheless, even with org.drools.core.common.ProjectClassLoader the issue remains, since the internal DRL conditions query are submitted as class names to resolve and with the number of rules growing in the system, the blacklisting of invalid class names is not enough any more: it would be desirable to have an internal hook to filter the names matching a configurable pattern. -- 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