October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2214) Allow additional environment properties to be set for outbound LDAP connections used by security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2214: ----------------------------------- Summary: Allow additional environment properties to be set for outbound LDAP connections used by security realms. (was: Allow existing environment properties to be set for outbound LDAP connections used by security realms.) > Allow additional environment properties to be set for outbound LDAP connections used by security realms. > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-2214 > URL: https://issues.jboss.org/browse/WFLY-2214 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > LDAP security realm needs to have configurable timeouts. > The default LDAP connection timeout appears to be 2 minutes. If the ldap server is down, it could take 2 minutes for the connection to timeout. This can cause unneeded delay if you have configured multiple ldap servers for failover / redundancy. > The following hack appears to work: > +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java > @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag > result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory); > String url = config.require(URL).asString(); > result.put(Context.PROVIDER_URL,url); > + result.put("com.sun.jndi.ldap.connect.timeout", "500"); > return result; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] from ASSIGNED to POST > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2414) Update to HAL 2.0.6.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-2414?page=com.atlassian.jira.plugin.... ] Harald Pehl reassigned WFLY-2414: --------------------------------- Assignee: Harald Pehl (was: Heiko Braun) > Update to HAL 2.0.6.Final > ------------------------- > > Key: WFLY-2414 > URL: https://issues.jboss.org/browse/WFLY-2414 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2414) Update to HAL 2.0.6.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-2414: --------------------------------- Summary: Update to HAL 2.0.6.Final Key: WFLY-2414 URL: https://issues.jboss.org/browse/WFLY-2414 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Reporter: Harald Pehl Assignee: Heiko Braun Fix For: 8.0.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-882) Improve error message for bad/incomplete XML in deployment scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-882?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on WFLY-882: --------------------------------------- An additional INFO message saying that would be good. There's a specific method that detects malformed xml that could log that without any changes elsewhere. Note the message in the JIRA description is at INFO. > Improve error message for bad/incomplete XML in deployment scanner > ------------------------------------------------------------------ > > Key: WFLY-882 > URL: https://issues.jboss.org/browse/WFLY-882 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Filip Nguyen > Assignee: Tomaz Cerar > Priority: Trivial > Attachments: loop-vdb.xml > > > Deploying VDB with invalid XML (closed translator tag). Causes following error: > [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2413) UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-2413: ------------------------------------- Summary: UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent Key: WFLY-2413 URL: https://issues.jboss.org/browse/WFLY-2413 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: CDI / Weld Reporter: Alessio Soldano Assignee: Stuart Douglas Fix For: 8.0.0.CR1 Attachments: jaxws-cxf-mixtype.war I'm getting a java.lang.UnsupportedOperationException when deploying one of the jbossws-cxf testsuite test archive (attached to the case). 17:17:31,212 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] Caused by: java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1069) [rt.jar:1.7.0_17] at org.jboss.as.weld.injection.WeldComponentService.findManagedBeanForWSComponent(WeldComponentService.java:174) at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] ... 3 more 17:17:31,235 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jaxws-cxf-mixtype.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service Caused by: java.lang.UnsupportedOperationException"}} 17:17:31,238 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jaxws-cxf-mixtype.war" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service Caused by: java.lang.UnsupportedOperationException"}} The problem is introduced by one of the commits in WFLY master listed at http://jbossws.jboss.org:8180/hudson/job/AS-8.0.0/267/changes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2413) UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-2413?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-2413: ---------------------------------- Attachment: jaxws-cxf-mixtype.war > UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent > ----------------------------------------------------------------------------------- > > Key: WFLY-2413 > URL: https://issues.jboss.org/browse/WFLY-2413 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Reporter: Alessio Soldano > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > Attachments: jaxws-cxf-mixtype.war > > > I'm getting a java.lang.UnsupportedOperationException when deploying one of the jbossws-cxf testsuite test archive (attached to the case). > 17:17:31,212 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.UnsupportedOperationException > at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1069) [rt.jar:1.7.0_17] > at org.jboss.as.weld.injection.WeldComponentService.findManagedBeanForWSComponent(WeldComponentService.java:174) > at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > ... 3 more > 17:17:31,235 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jaxws-cxf-mixtype.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service > Caused by: java.lang.UnsupportedOperationException"}} > 17:17:31,238 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jaxws-cxf-mixtype.war" was rolled back with the following failure message: > {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service > Caused by: java.lang.UnsupportedOperationException"}} > The problem is introduced by one of the commits in WFLY master listed at http://jbossws.jboss.org:8180/hudson/job/AS-8.0.0/267/changes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> made a comment on [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] Yes is it a one line fix (two if you count the closing bracket of the if statement) ;-) Pull requests coming shortly. > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] from CLOSED to ASSIGNED > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] Good catch Darran. I'm re-opening with a changed title. The fix is to remove those from the metadata. > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013