March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2408) Add TRACE logging for connection properties used to connect to LDAP from realm.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2408?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2408: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 974324|https://bugzilla.redhat.com/show_bug.cgi?id=974324] from MODIFIED to ON_QA > Add TRACE logging for connection properties used to connect to LDAP from realm. > ------------------------------------------------------------------------------- > > Key: WFLY-2408 > URL: https://issues.jboss.org/browse/WFLY-2408 > 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 > > -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-352) Add sufficient TRACE / DEBUG logging to debug security realm configurations.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-352?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-352: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 974324|https://bugzilla.redhat.com/show_bug.cgi?id=974324] from MODIFIED to ON_QA > Add sufficient TRACE / DEBUG logging to debug security realm configurations. > ---------------------------------------------------------------------------- > > Key: WFLY-352 > URL: https://issues.jboss.org/browse/WFLY-352 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Eric Rich > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.Beta1 > > Attachments: jboss-as-domain-management-7.1.2.Final-redhat-1.jar, log_mgmt_auth_calls.txt > > > When trying to diagnose LDAP or Admin Configuration issue in Domain mode there is currently no logging for any of the authentication information. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3125) Update help text for add-user to reflect that password is checked against the configured policy.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3125?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3125: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1063888|https://bugzilla.redhat.com/show_bug.cgi?id=1063888] from MODIFIED to ON_QA > Update help text for add-user to reflect that password is checked against the configured policy. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3125 > URL: https://issues.jboss.org/browse/WFLY-3125 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3133) Misleading error message for add-user username requirements.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3133?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3133: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1062611|https://bugzilla.redhat.com/show_bug.cgi?id=1062611] from MODIFIED to ON_QA > Misleading error message for add-user username requirements. > ------------------------------------------------------------ > > Key: WFLY-3133 > URL: https://issues.jboss.org/browse/WFLY-3133 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > The current error message is: - > {code} > JBAS015239: Only alpha/numeric usernames accepted. > {code} > However a small set of symbols are allowed. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3161) Optimize org.jboss.as.jmx.model.RootResourceIterator

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3161: -------------------------------------- Summary: Optimize org.jboss.as.jmx.model.RootResourceIterator Key: WFLY-3161 URL: https://issues.jboss.org/browse/WFLY-3161 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management, JMX Affects Versions: 8.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 9.0.0.CR1 RootResourceIterator is performing an access control check on a resource before confirming that the caller is in any way interested in that resource. This results in spurious access control checks. Fixing this can speed up queryMBeans and queryNames calls. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1157) Kerberos support

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1157: -------------------------------------- Summary: Kerberos support Key: JBJCA-1157 URL: https://issues.jboss.org/browse/JBJCA-1157 Project: IronJacamar Issue Type: Task Components: JDBC Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.25.Final, 1.1.5.Final, 1.2.0.Beta1 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2654) The run-as identity does NOT apply to the timeout callback method of an enterprise bean

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-2654?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned WFLY-2654: ------------------------------------ Assignee: Tomasz Adamski (was: Stuart Douglas) > The run-as identity does NOT apply to the timeout callback method of an enterprise bean > --------------------------------------------------------------------------------------- > > Key: WFLY-2654 > URL: https://issues.jboss.org/browse/WFLY-2654 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Matus Abaffy > Assignee: Tomasz Adamski > > EJB 3.2 spec., 12.3.4.1 Run-as: > bq. The run-as identity applies ... to the timeout callback methods of an enterprise bean; > Assume the following classes: > {code} > @Stateless > @RunAs("alarm") > public class Alarm { > @EJB > private Bell bell; > // some more logic > @Timeout > public void ejbTimeout(Timer timer) { > bell.ring(); > } > } > {code} > {code} > @Stateless > @RolesAllowed("alarm") > public class Bell { > public void ring() {} > } > {code} > When the Alarm's timeout callback method is invoked due to timer expiration, bell.ring(); results in > {code}ERROR [org.jboss.as.ejb3.invocation] (EJB default - 1) JBAS014134: EJB Invocation failed on component Bell for method public void org.jboss.as.test.integration.ejb.security.timeout.Bell.ring(): javax.ejb.EJBAccessException: JBAS014502: Invocation on method: public void org.jboss.as.test.integration.ejb.security.timeout.Bell.ring() of bean: Bell is not allowed {code} > Calling bell.ring(); from Alarm's business methods works as expected (no error). > Simple test case available at: https://github.com/bafco/wildfly/tree/timeoutSecurity -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2669) ConcurrentModificationException releasing JSF factories

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-2669?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-2669: ---------------------------------- JAVASERVERFACES-3202 has now been resolved. The fix will be included in the Mojarra 2.2.7 release. > ConcurrentModificationException releasing JSF factories > ------------------------------------------------------- > > Key: WFLY-2669 > URL: https://issues.jboss.org/browse/WFLY-2669 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.Beta1 > Reporter: Jozef Hartinger > Assignee: Farah Juma > > Saw this happen once. Probably a thread-safety problem in JSF API: > {code} > 5:04:37,876 ERROR [io.undertow.servlet.request] (MSC service thread 1-4) UT015005: Error invoking method contextDestroyed on listener class com.sun.faces.config.ConfigureListener: java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926) [rt.jar:1.7.0_45] > at java.util.HashMap$ValueIterator.next(HashMap.java:954) [rt.jar:1.7.0_45] > at javax.faces.FactoryFinder.releaseFactories(FactoryFinder.java:440) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at com.sun.faces.config.ConfigManager.releaseFactories(ConfigManager.java:808) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.config.ConfigManager.destroy(ConfigManager.java:474) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:329) [jsf-impl-2.2.4-jbossorg-1.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Beta27.jar:1.0.0.Beta27] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Beta27.jar:1.0.0.Beta27] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:523) [undertow-servlet-1.0.0.Beta27.jar:1.0.0.Beta27] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > 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] > {code} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2509) Method invocation of a non serializable remote EJB

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-2509?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned WFLY-2509: ------------------------------------ Assignee: Tomasz Adamski (was: David Lloyd) > Method invocation of a non serializable remote EJB > --------------------------------------------------- > > Key: WFLY-2509 > URL: https://issues.jboss.org/browse/WFLY-2509 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: EJB > Reporter: omar al kababji > Assignee: Tomasz Adamski > Priority: Optional > > If you have a remote EJB that is not Serializable (i.e. does not implement the interface Serializable) you can lookup such class from a remote EJB client however when you execute a method you get an error as follows: > java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling > The enhancement is to give an error or warning message when the EJB is deployed notifying the developer that he is deploying a Remote EJB that is not implementing the Serializable interface. > The same thing happens if you deploy an EJB marked with the annotation @Remote but with no @Stateless nor @Statefull annotations. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3053) BootstrapImpl#bootstrap result is inherently racy

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFLY-3053?page=com.atlassian.jira.plugin.... ] Richard Opalka reassigned WFLY-3053: ------------------------------------ Assignee: Richard Opalka (was: Jason Greene) > BootstrapImpl#bootstrap result is inherently racy > ------------------------------------------------- > > Key: WFLY-3053 > URL: https://issues.jboss.org/browse/WFLY-3053 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Reporter: David Lloyd > Assignee: Richard Opalka > Fix For: 8.0.1.Final > > > The boostrap code presently installs a stability monitor and awaits stability before returning. It then probes the state of the root service. There is a window of time in which the root service may be stopped or removed, resulting in big exception traces being logged. To atomically get the result of the operation, the service container must somehow be frozen until the root service is completely read. -- 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

12 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 March 2014