September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3916) Eliminate customized usage of RuntimePermission

by David Lloyd (JIRA)

David Lloyd created WFLY-3916: --------------------------------- Summary: Eliminate customized usage of RuntimePermission Key: WFLY-3916 URL: https://issues.jboss.org/browse/WFLY-3916 Project: WildFly Issue Type: Task Components: Naming Reporter: David Lloyd Assignee: Eduardo Martins Fix For: 9.0.0.CR1 The JDK defines the entire domain of valid RuntimePermission names. Here's a listing: {noformat} org.jboss.as.naming.NamingContext#SET_ACTIVE_NAMING_STORE org.jboss.as.security.remoting.RemotingContext#SET_CONNECTION_PERMISSION org.jboss.as.security.remoting.RemotingContext#CLEAR_CONNECTION_PERMISSION org.jboss.as.security.remoting.RemotingContext#GET_CONNECTION_PERMISSION org.jboss.as.security.remoting.RemotingContext#IS_SET_PERMISSION {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-131) Upgrade JBoss VFS

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-131?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFCORE-131: ------------------------------------ VFS 3.2.7.Final should include this fix. > Upgrade JBoss VFS > ----------------- > > Key: WFCORE-131 > URL: https://issues.jboss.org/browse/WFCORE-131 > Project: WildFly Core > Issue Type: Component Upgrade > Components: VFS > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 1.0.0.CR1 > > > Upgrade VFS to a version which includes a fix for JBVFS-197. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

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: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1147603|https://bugzilla.redhat.com/show_bug.cgi?id=1147603] from POST to CLOSED > 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)

11 years, 7 months

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: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1147603|https://bugzilla.redhat.com/show_bug.cgi?id=1147603] from NEW to POST > 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)

11 years, 7 months

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 updated WFCORE-134: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=980923 > 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 > > 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)

11 years, 7 months

1
0
0 / 0

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

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFCORE-134: ---------------------------------------- Summary: 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 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)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-83) EAR deployment overlay did not work if there is no related resource included in the ear

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-83?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-83: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1145364|https://bugzilla.redhat.com/show_bug.cgi?id=1145364] from ON_QA to VERIFIED > EAR deployment overlay did not work if there is no related resource included in the ear > --------------------------------------------------------------------------------------- > > Key: WFCORE-83 > URL: https://issues.jboss.org/browse/WFCORE-83 > Project: WildFly Core > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha6 > > Attachments: reproducer.zip > > > It is possible to overlay WEB-inf/lib/xy.jar without having xy.jar included in the war file. > If an EAR file is used a module in the lib directory can not be added in the same way. But overlay is working if the lib/xy.jar is available. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3888) Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3888?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3888: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1145896|https://bugzilla.redhat.com/show_bug.cgi?id=1145896] from ON_QA to VERIFIED > Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly > --------------------------------------------------------------------------------------------- > > Key: WFLY-3888 > URL: https://issues.jboss.org/browse/WFLY-3888 > Project: WildFly > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > > All ERROR and WARN messages should show the full timer information, specially the customer timer-information. > This will make it more easy to identify the exact timer in case of an EJB object has multiple timer instances active. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[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: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1105677|https://bugzilla.redhat.com/show_bug.cgi?id=1105677] from POST to MODIFIED > 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)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reopened WFLY-3913: ------------------------------- After discussion [~dlofthouse] we decided we should remove requirement on https socket-binding and report error if not set when needed > HTTPS socket-binding definition always needed > --------------------------------------------- > > Key: WFLY-3913 > URL: https://issues.jboss.org/browse/WFLY-3913 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Jose Monreal > Assignee: Tomaz Cerar > Labels: https, standalone > Fix For: 8.2.0.CR1, 9.0.0.CR1 > > Attachments: standalone.xml, standalone.xml > > > When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors. > The errors are the following: > {noformat} > 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("http-listener" => "default") > ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]} > 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => ["jboss.ws.config"], > "Services that may be the cause:" => [ > "jboss.binding.https", > "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" > ] > }} > 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([ > ("subsystem" => "ejb3"), > ("service" => "remote") > ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]} > 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default] > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector] > > 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014