October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-128) Nonexistent ldap group causes authentication to fail in security-realm

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-128?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-128: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1105677|https://bugzilla.redhat.com/show_bug.cgi?id=1105677] from MODIFIED to ON_QA > Nonexistent ldap group causes authentication to fail in security-realm > ----------------------------------------------------------------------- > > Key: WFCORE-128 > URL: https://issues.jboss.org/browse/WFCORE-128 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha9 > > > The LdapGroupSearcher code will fail if it tries to lookup a group that > does not exist on the local ldap server. > This can happen when the ldap systems are configured as trusted domains. > Even though the security-realm is not configured to use the trusted domain > (it is configured to only look at a single ldap server), the > user's entry on one ldap server could point at a group that exists on > the other (trusted) ldap server. > The LdapGroupSearcher code attempts to lookup this role and it fails. This > failure is sent back to the http server which results in an HTTP 500 error > and leaves the user with no way to authenticate/login. > There is currently not a way to tell the group searcher code to ignore the > group/role that cannot be found. > 2014-06-06 12:44:39,819 TRACE [org.jboss.as.domain.management.security] (XNIO-1 task-1) Group found with distinguishedName=cn=TestManagedRole,ou=People,dc=my-ds-domain,dc=com > 2014-06-06 12:44:39,821 TRACE [org.jboss.as.domain.management.security] (XNIO-1 task-1) Failure supplementing Subject: javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'cn=TestManagedRole,ou=People,dc=my-ds-domain,dc=com' > at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3112) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.c_getAttributes(LdapCtx.java:1332) [rt.jar:1.7.0_45] > at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(ComponentDirContext.java:231) [rt.jar:1.7.0_45] > at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:139) [rt.jar:1.7.0_45] > at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(PartialCompositeDirContext.java:127) [rt.jar:1.7.0_45] > at javax.naming.directory.InitialDirContext.getAttributes(InitialDirContext.java:142) [rt.jar:1.7.0_45] > at javax.naming.directory.InitialDirContext.getAttributes(InitialDirContext.java:142) [rt.jar:1.7.0_45] > at org.jboss.as.domain.management.security.LdapGroupSearcherFactory$PrincipalToGroupSearcher.search(LdapGroupSearcherFactory.java:256) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.management.security.LdapGroupSearcherFactory$PrincipalToGroupSearcher.search(LdapGroupSearcherFactory.java:191) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.management.security.LdapCacheService$NoCacheCache.search(LdapCacheService.java:223) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.management.security.LdapSubjectSupplementalService$LdapSubjectSupplemental.loadGroupEntries(LdapSubjectSupplementalService.java:218) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.management.security.LdapSubjectSupplementalService$LdapSubjectSupplemental.loadGroups(LdapSubjectSupplementalService.java:195) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.management.security.LdapSubjectSupplementalService$LdapSubjectSupplemental.loadGroups(LdapSubjectSupplementalService.java:188) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.management.security.LdapSubjectSupplementalService$LdapSubjectSupplemental.supplementSubject(LdapSubjectSupplementalService.java:163) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.management.security.SecurityRealmService$1.createSubjectUserInfo(SecurityRealmService.java:200) [wildfly-domain-management-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.http.server.security.RealmIdentityManager.verify(RealmIdentityManager.java:155) [wildfly-domain-http-interface-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.domain.http.server.security.RealmIdentityManager.verify(RealmIdentityManager.java:120) [wildfly-domain-http-interface-8.1.0.Final.jar:8.1.0.Final] > at io.undertow.security.impl.BasicAuthenticationMechanism.authenticate(BasicAuthenticationMechanism.java:110) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at org.jboss.as.domain.http.server.security.AuthenticationMechanismWrapper.authenticate(AuthenticationMechanismWrapper.java:57) [wildfly-domain-http-interface-8.1.0.Final.jar:8.1.0.Final] > at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:281) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:298) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:268) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:131) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:106) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:99) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:50) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:177) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.15.Final.jar:1.0.15.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1213) XA_RBEND should be included in check

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1213?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1213: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1147419|https://bugzilla.redhat.com/show_bug.cgi?id=1147419] from MODIFIED to ON_QA > XA_RBEND should be included in check > ------------------------------------ > > Key: JBJCA-1213 > URL: https://issues.jboss.org/browse/JBJCA-1213 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1179) Guard against Subject modification

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1179?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1179: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1091419|https://bugzilla.redhat.com/show_bug.cgi?id=1091419] from MODIFIED to ON_QA > Guard against Subject modification > ---------------------------------- > > Key: JBJCA-1179 > URL: https://issues.jboss.org/browse/JBJCA-1179 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta2 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > Attachments: ironjacamar-jdbc.jar > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1650) Legacy subsystem testing needs some classloading exclusion mecanism

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1650?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1650: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from MODIFIED to ON_QA > Legacy subsystem testing needs some classloading exclusion mecanism > ------------------------------------------------------------------- > > Key: WFLY-1650 > URL: https://issues.jboss.org/browse/WFLY-1650 > Project: WildFly > Issue Type: Bug > Components: Logging, Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Fix For: 8.0.0.Beta1 > > > When translation messages are used (which is the case of EAP) we have conflicts between generated $logger classes when testing submodules. > Some $logger classes exis thus they are loaded by the parent classloader before the childfirstclassloader tries to load them, thus we have a potential ClassCastException brewing. > For exemple this breaks the EAP build on a French OS. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1215) Only use XidWrapper if needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1215?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1215: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1147715|https://bugzilla.redhat.com/show_bug.cgi?id=1147715] from MODIFIED to ON_QA > Only use XidWrapper if needed > ----------------------------- > > Key: JBJCA-1215 > URL: https://issues.jboss.org/browse/JBJCA-1215 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBMETA-379) Missing param-name in a web.xml causes NullPointerException during deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-379?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-379: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1125421|https://bugzilla.redhat.com/show_bug.cgi?id=1125421] from MODIFIED to ON_QA > Missing param-name in a web.xml causes NullPointerException during deployment > ------------------------------------------------------------------------------ > > Key: JBMETA-379 > URL: https://issues.jboss.org/browse/JBMETA-379 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 8.0.0.Final > Reporter: Jay Kumar SenSharma > Assignee: Jean-Frederic Clere > Fix For: 8.0.1.Final > > Attachments: ContextParamNullDemo.war > > > - While deploying a WAR, If the web.xml file is used which has context <param-value> defined, However it has missing <param-name> then it causes NullPointerException as following: > {code} > 00:12:09,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "ContextParamNullDemo.war" (runtime-name: "ContextParamNullDemo.war") > 00:12:09,591 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."ContextParamNullDemo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ContextParamNullDemo.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "ContextParamNullDemo.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) [wildfly-server-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > Caused by: java.lang.NullPointerException > at org.jboss.as.jsf.deployment.JSFVersionProcessor.deploy(JSFVersionProcessor.java:91) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) [wildfly-server-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > ... 5 more > 00:12:09,598 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ContextParamNullDemo.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ContextParamNullDemo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ContextParamNullDemo.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"ContextParamNullDemo.war\" > Caused by: java.lang.NullPointerException"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1212) Pool could keep connections open after shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1212?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1212: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1147412|https://bugzilla.redhat.com/show_bug.cgi?id=1147412] from MODIFIED to ON_QA > Pool could keep connections open after shutdown > ----------------------------------------------- > > Key: JBJCA-1212 > URL: https://issues.jboss.org/browse/JBJCA-1212 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > > Let MCP check pool status before scheduling prefill -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-134) Make sure CLIWrapper doesn't use default encoding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-134: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from MODIFIED to ON_QA > Make sure CLIWrapper doesn't use default encoding > ------------------------------------------------- > > Key: WFCORE-134 > URL: https://issues.jboss.org/browse/WFCORE-134 > Project: WildFly Core > Issue Type: Bug > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 1.0.0.Alpha9 > > > CLIWrapper is using the default encoding which might lead to issue with non US locales. > Also take advantage of this fix to remove some hard coded strings from tests. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1332) Integrate the compressed message support that was introduced in EJB client library

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1332?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1332: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1149020|https://bugzilla.redhat.com/show_bug.cgi?id=1149020] from MODIFIED to ON_QA > Integrate the compressed message support that was introduced in EJB client library > ---------------------------------------------------------------------------------- > > Key: WFLY-1332 > URL: https://issues.jboss.org/browse/WFLY-1332 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha2 > > > https://issues.jboss.org/browse/EJBCLIENT-76 introduced a feature where the message stream that contains the EJB protocol message can be compressed. This involves a new message header which the server needs to support for the compression to be functional. This JIRA tracks the server side additions to support this feature. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-138) Upgrade log4j-jboss-logmanager from 1.1.0.Final to 1.1.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-138?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-138: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1148632|https://bugzilla.redhat.com/show_bug.cgi?id=1148632] from MODIFIED to ON_QA > Upgrade log4j-jboss-logmanager from 1.1.0.Final to 1.1.1.Final > -------------------------------------------------------------- > > Key: WFCORE-138 > URL: https://issues.jboss.org/browse/WFCORE-138 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

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 2014