April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8545) WildFly Elytron tool has to have own sh script

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8545?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8545: ----------------------------------- Summary: WildFly Elytron tool has to have own sh script (was: CS tool has to have own sh script) > WildFly Elytron tool has to have own sh script > ---------------------------------------------- > > Key: WFLY-8545 > URL: https://issues.jboss.org/browse/WFLY-8545 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > CS tool has to have own sh script -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8545) WildFly Elytron tool has to have own sh script

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8545?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8545: ----------------------------------- Description: WildFly Elytron tool has to have own sh script was: CS tool has to have own sh script > WildFly Elytron tool has to have own sh script > ---------------------------------------------- > > Key: WFLY-8545 > URL: https://issues.jboss.org/browse/WFLY-8545 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > WildFly Elytron tool has to have own sh script -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1199) Memory leak in KieScanner

by Ajinkya Vaze (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1199?page=com.atlassian.jira.plugi... ] Ajinkya Vaze commented on DROOLS-1199: -------------------------------------- Is this issue fixed in version 6.5.0.Final? > Memory leak in KieScanner > ------------------------- > > Key: DROOLS-1199 > URL: https://issues.jboss.org/browse/DROOLS-1199 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Viacheslav Krot > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > I'm not sure, but it seems there is a memory leak in KieScanner, not in scanner directly, but somewhere in plexus used internally. > If you start KieScanner with version = LATEST, start it with interval say 1 second and sample memory with visualvm (or any other), you can watch number of instances org.eclipse.sisu.plexus.* growing over time. And they cannot be garbage collected - memory root is timer thread. This happens in drools 6.4.0, in 6.3.0 this issue was absent. > Eventually application fails with OOM. > As a workaround we call KieScanner#scan manually in a separate thread pool that is recreated from time to time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2648) HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue

by Ondrej Kotek (JIRA)

Ondrej Kotek created WFCORE-2648: ------------------------------------ Summary: HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue Key: WFCORE-2648 URL: https://issues.jboss.org/browse/WFCORE-2648 Project: WildFly Core Issue Type: Bug Components: Remoting, Test Suite Reporter: Ondrej Kotek Assignee: Darran Lofthouse Priority: Blocker Fix For: 3.0.0.Beta15 The listed test case is failing during clean up with the following error: - {noformat} java.io.IOException: java.io.IOException: WFLYPRT0054: Channel closed at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80) {noformat} The stage of the test using HTTP Upgrade over a HTTPS connection appears to be working fine, the issue is with the native management interface used for test clean up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2647) Add an option to always send the client SSL certificate to LDAP server

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2647?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-2647: ------------------------------------------ Sounds reasonable with one additional requirement. The system property should only be resolved within the OperationStepHandler - it should not be dynamically resolved at runtime. > Add an option to always send the client SSL certificate to LDAP server > ---------------------------------------------------------------------- > > Key: WFCORE-2647 > URL: https://issues.jboss.org/browse/WFCORE-2647 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is the component issue for https://issues.jboss.org/browse/JBEAP-4439 and https://bugzilla.redhat.com/show_bug.cgi?id=1327758 > The present code in {{LdapConnectionManagerService}} was designed so that the client cert is sent to authenticate the search account but during the username / password verification step, the client cert is not sent. > The present objective is to add an option (that will default to the old behavior) to send the client password also during the username / password verification. > This includes (citing [~dlofthouse]): > * Implement management model based configuration and an implementation for the current version > * Port back to older versions using a system property. > * Forward port the system property to the current version for compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2647) Add an option to always send the client SSL certificate to LDAP server

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2647?page=com.atlassian.jira.plugi... ] Peter Palaga edited comment on WFCORE-2647 at 4/10/17 7:09 AM: --------------------------------------------------------------- [~dlofthouse] could you please approve the following choices or propose something better? (1) The new management attribute will be called {{alwaysSendClientCert}} and its values will be {{false}} : default, the present behavior and {{true}} {{LdapConnectionManagerService.verifyIdentity(Config, String, String)}} will call {{getSSLContext(false)}} (2) The new management attribute will hang on the ldap outbound-connection node (3) The system property will be called {{jboss.as.management.outbound.ldap.alwaysSendClientCert}} was (Author: ppalaga): [~dlofthouse] could you please approve the following choices? (1) The new management attribute will be called {{alwaysSendClientCert}} and its values will be {{false}} : default, the present behavior and {{true}} {{LdapConnectionManagerService.verifyIdentity(Config, String, String)}} will call {{getSSLContext(false)}} (2) The new management attribute will hang on the ldap outbound-connection node (3) The system property will be called {{jboss.as.management.outbound.ldap.alwaysSendClientCert}} > Add an option to always send the client SSL certificate to LDAP server > ---------------------------------------------------------------------- > > Key: WFCORE-2647 > URL: https://issues.jboss.org/browse/WFCORE-2647 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is the component issue for https://issues.jboss.org/browse/JBEAP-4439 and https://bugzilla.redhat.com/show_bug.cgi?id=1327758 > The present code in {{LdapConnectionManagerService}} was designed so that the client cert is sent to authenticate the search account but during the username / password verification step, the client cert is not sent. > The present objective is to add an option (that will default to the old behavior) to send the client password also during the username / password verification. > This includes (citing [~dlofthouse]): > * Implement management model based configuration and an implementation for the current version > * Port back to older versions using a system property. > * Forward port the system property to the current version for compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2647) Add an option to always send the client SSL certificate to LDAP server

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2647?page=com.atlassian.jira.plugi... ] Peter Palaga commented on WFCORE-2647: -------------------------------------- [~dlofthouse] could you please approve the following choices? (1) The new management attribute will be called {{alwaysSendClientCert}} and its values will be {{false}} : default, the present behavior and {{true}} {{LdapConnectionManagerService.verifyIdentity(Config, String, String)}} will call {{getSSLContext(false)}} (2) The new management attribute will hang on the ldap outbound-connection node (3) The system property will be called {{jboss.as.management.outbound.ldap.alwaysSendClientCert}} > Add an option to always send the client SSL certificate to LDAP server > ---------------------------------------------------------------------- > > Key: WFCORE-2647 > URL: https://issues.jboss.org/browse/WFCORE-2647 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is the component issue for https://issues.jboss.org/browse/JBEAP-4439 and https://bugzilla.redhat.com/show_bug.cgi?id=1327758 > The present code in {{LdapConnectionManagerService}} was designed so that the client cert is sent to authenticate the search account but during the username / password verification step, the client cert is not sent. > The present objective is to add an option (that will default to the old behavior) to send the client password also during the username / password verification. > This includes (citing [~dlofthouse]): > * Implement management model based configuration and an implementation for the current version > * Port back to older versions using a system property. > * Forward port the system property to the current version for compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2647) Add an option to always send the client SSL certificate to LDAP server

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2647?page=com.atlassian.jira.plugi... ] Peter Palaga updated WFCORE-2647: --------------------------------- Steps to Reproduce: Reproducible with OpenLDAP. See https://github.com/ppalaga/WFCORE-2647 for a detailed step-by-step instructions. > Add an option to always send the client SSL certificate to LDAP server > ---------------------------------------------------------------------- > > Key: WFCORE-2647 > URL: https://issues.jboss.org/browse/WFCORE-2647 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is the component issue for https://issues.jboss.org/browse/JBEAP-4439 and https://bugzilla.redhat.com/show_bug.cgi?id=1327758 > The present code in {{LdapConnectionManagerService}} was designed so that the client cert is sent to authenticate the search account but during the username / password verification step, the client cert is not sent. > The present objective is to add an option (that will default to the old behavior) to send the client password also during the username / password verification. > This includes (citing [~dlofthouse]): > * Implement management model based configuration and an implementation for the current version > * Port back to older versions using a system property. > * Forward port the system property to the current version for compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2647) Add an option to always send the client SSL certificate to LDAP server

by Peter Palaga (JIRA)

Peter Palaga created WFCORE-2647: ------------------------------------ Summary: Add an option to always send the client SSL certificate to LDAP server Key: WFCORE-2647 URL: https://issues.jboss.org/browse/WFCORE-2647 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Peter Palaga Assignee: Peter Palaga This is the component issue for https://issues.jboss.org/browse/JBEAP-4439 and https://bugzilla.redhat.com/show_bug.cgi?id=1327758 The present code in {{LdapConnectionManagerService}} was designed so that the client cert is sent to authenticate the search account but during the username / password verification step, the client cert is not sent. The present objective is to add an option (that will default to the old behavior) to send the client password also during the username / password verification. This includes (citing [~dlofthouse]): * Implement management model based configuration and an implementation for the current version * Port back to older versions using a system property. * Forward port the system property to the current version for compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6194) Tests fail with "java.util.PropertyPermission" with security manager enabled

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-6194?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-6194: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/8800, https://github.com/wildfly/wildfly/pull/9916, https://github.com/wildfly-security-incubator/wildfly/pull/181 (was: https://github.com/wildfly/wildfly/pull/8800, https://github.com/wildfly/wildfly/pull/9916) > Tests fail with "java.util.PropertyPermission" with security manager enabled > ---------------------------------------------------------------------------- > > Key: WFLY-6194 > URL: https://issues.jboss.org/browse/WFLY-6194 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Ivo Studensky > > *org.jboss.as.test.integration.ee.injection.support.websocket.WebSocketInjectionSupportTestCase#testWebSocketInjectionAndInterception* > *org.jboss.as.test.integration.ee.suspend.EEConcurrencySuspendTestCase#testRequestInShutdown* > {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.ee.injection.support.websocket.WebSocketInjectionSupportTestCase#testWebSocketInjectionAndInterception}} > {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.ee.suspend.EEConcurrencySuspendTestCase#testRequestInShutdown}} > Fail with: > {code} > java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "management.address" "read")" in code source "(vfs:/content/ee-suspend.war/WEB-INF/classes <no signer certificates>)" of "null") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273) > at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:496) > at java.lang.System.getProperty(System.java:717) > at org.jboss.as.test.shared.TestSuiteEnvironment.getServerAddress(TestSuiteEnvironment.java:77) > at org.jboss.as.test.integration.ee.suspend.EEConcurrencySuspendTestCase.testRequestInShutdown(EEConcurrencySuspendTestCase.java:77) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 April 2017