January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-342) Reenable ClusteredSingleSignOnTestCase test to work with Undertow

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-342?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-342: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > Reenable ClusteredSingleSignOnTestCase test to work with Undertow > ------------------------------------------------------------------ > > Key: WFLY-342 > URL: https://issues.jboss.org/browse/WFLY-342 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Kabir Khan > Assignee: Paul Ferraro > Priority: Critical > Fix For: 9.0.0.CR1 > > Attachments: ClusteredSingleSignOnTestCase1.html, ClusteredSingleSignOnTestCase2.html, ClusteredSingleSignOnTestCase3.html > > > Test have been @Ignored until Undertow implements SSO. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2774) Non-distributed, stateful web applications cannot be load balanced using sticky sessions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2774?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-2774: ------------------------------------ This should be resolved once CR2 of undertow is included > Non-distributed, stateful web applications cannot be load balanced using sticky sessions > ---------------------------------------------------------------------------------------- > > Key: WFLY-2774 > URL: https://issues.jboss.org/browse/WFLY-2774 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 8.0.0.Final > > > In AS7, one could configure a load balancer with sticky sessions to support load balancing for non-distributed web applications. > While the distributed session manager supports parsing and formatting of the instance-id from/to the session id, the in-memory session manager does not. > The use case for this are stateful web applications that do not require high-availability of state (e.g. a stateless web-app that uses container managed authentication), but would also like to scale beyond the capacity of a single server. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1535) SSLEJBRemoteClientTestCase runs into intermittent failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1535?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1535: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > SSLEJBRemoteClientTestCase runs into intermittent failures > ---------------------------------------------------------- > > Key: WFLY-1535 > URL: https://issues.jboss.org/browse/WFLY-1535 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: jaikiran pai > Assignee: Paul Ferraro > Priority: Critical > Fix For: 9.0.0.CR1 > > > SSLEJBRemoteClientTestCase runs into intermittent failures on TeamCity. To make matters worse, a failure in one test method can have a side effect on other test methods in that testcase, given the way it's written. The entire run is here http://teamcity.cafe-babe.org/viewLog.html?buildId=5251&tab=buildResultsD.... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2641) ARQ upgrade likely to cause test failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2641?page=com.atlassian.jira.plugin.... ] Jason Greene reassigned WFLY-2641: ---------------------------------- Assignee: Jason Greene (was: Aslak Knutsen) > ARQ upgrade likely to cause test failures > ------------------------------------------ > > Key: WFLY-2641 > URL: https://issues.jboss.org/browse/WFLY-2641 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.CR1 > > > {code} > testSimpleBundleWithWabExtension(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.028 sec <<< ERROR! > java.lang.NullPointerException: null > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:290) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2592) A server-to-server communication via outbound connection is not working

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2592?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2592: ------------------------------- Priority: Critical (was: Blocker) > A server-to-server communication via outbound connection is not working > ----------------------------------------------------------------------- > > Key: WFLY-2592 > URL: https://issues.jboss.org/browse/WFLY-2592 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, Remoting > Affects Versions: 8.0.0.Beta1 > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Critical > Labels: ejb, remoting > Attachments: networktraffic, server-client.log, server-server.log > > > A ejb invocation from a SLSB is configured similar to AS7 (EAP6) to call a remote server fail in WildFly with the ERROR message " EJBCLIENT000025: No EJB receiver available for handling". > The logfiles of client(server) and remote-server are attached, also a WireShark dump of the related network traffic. > A standalone client at the same machine is able to call the remote application. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2641) ARQ upgrade likely to cause test failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2641?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-2641: ------------------------------------ We will revisit our test suite in WF9, including whether or not we stick with Arquillian. > ARQ upgrade likely to cause test failures > ------------------------------------------ > > Key: WFLY-2641 > URL: https://issues.jboss.org/browse/WFLY-2641 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Priority: Blocker > Fix For: 9.0.0.CR1 > > > {code} > testSimpleBundleWithWabExtension(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.028 sec <<< ERROR! > java.lang.NullPointerException: null > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:290) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2641) ARQ upgrade likely to cause test failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2641?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2641: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > ARQ upgrade likely to cause test failures > ------------------------------------------ > > Key: WFLY-2641 > URL: https://issues.jboss.org/browse/WFLY-2641 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Priority: Blocker > Fix For: 9.0.0.CR1 > > > {code} > testSimpleBundleWithWabExtension(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.028 sec <<< ERROR! > java.lang.NullPointerException: null > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:290) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2739) BeanDeploymentArchive for external (WFLY) modules added twice

by Pëtr Andreev (JIRA)

[ https://issues.jboss.org/browse/WFLY-2739?page=com.atlassian.jira.plugin.... ] Pëtr Andreev edited comment on WFLY-2739 at 1/31/14 5:01 PM: ------------------------------------------------------------- Pull Request: https://github.com/wildfly/wildfly/pull/5838 was (Author: pjotrovsky): Pull Request: https://github.com/wildfly/wildfly/pull/5828 > BeanDeploymentArchive for external (WFLY) modules added twice > ------------------------------------------------------------- > > Key: WFLY-2739 > URL: https://issues.jboss.org/browse/WFLY-2739 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.CR1 > Environment: Win7,CentOS6 > Reporter: Pëtr Andreev > Assignee: Jozef Hartinger > Fix For: 8.0.0.Final > > > The Weld-WFLY integration adds a dependency on WFLY module twice if the application deployment unit is an EAR containg libs, ejbs, war, etc. It prevents an application having dependencies on a new Picketlink (PL) extension to be deployed since PL contains a portable extension which has to be injected within PL module. The Weld-validation of the second time injection fails. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2854) '**' role incorrectly returns false from isUserInRole when user is authenticated

by arjan tijms (JIRA)

[ https://issues.jboss.org/browse/WFLY-2854?page=com.atlassian.jira.plugin.... ] arjan tijms updated WFLY-2854: ------------------------------ Description: When authentication has taken place in a web application such that {{HttpServletRequest#getUserPrincipal}} does not return null, testing for role '**' using {{HttpServletRequest#isUserInRole}} returns false. This is not correct. According to Servlet 13.3: {quote} {noformat} If the role-name of the security-role to be tested is “**”, and the application has NOT declared an application security-role with role-name “**”, isUserInRole must only return true if the user has been authenticated; {noformat} {quote} This is demonstrated by the following test: https://github.com/arjantijms/javaee7-samples/blob/master/jacc/contexts/s... was: When authentication has taken place in a web application such that {{HttpServletRequest#getUserprincipap}} does not return null, testing for role '**' using {{HttpServletRequest#isUserInRole}} returns false. This is not correct. According to Servlet 13.3: {quote} {noformat} If the role-name of the security-role to be tested is “**”, and the application has NOT declared an application security-role with role-name “**”, isUserInRole must only return true if the user has been authenticated; {noformat} {quote} This is demonstrated by the following test: https://github.com/arjantijms/javaee7-samples/blob/master/jacc/contexts/s... > '**' role incorrectly returns false from isUserInRole when user is authenticated > -------------------------------------------------------------------------------- > > Key: WFLY-2854 > URL: https://issues.jboss.org/browse/WFLY-2854 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.0.0.CR1 > Reporter: arjan tijms > Assignee: Darran Lofthouse > Labels: role, roles, security, servlet > > When authentication has taken place in a web application such that {{HttpServletRequest#getUserPrincipal}} does not return null, testing for role '**' using {{HttpServletRequest#isUserInRole}} returns false. > This is not correct. According to Servlet 13.3: > {quote} > {noformat} > If the role-name of the security-role to be tested is “**”, > and the application has NOT declared an application security-role with > role-name “**”, isUserInRole must only return true if the user has been > authenticated; > {noformat} > {quote} > This is demonstrated by the following test: > https://github.com/arjantijms/javaee7-samples/blob/master/jacc/contexts/s... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2854) '**' role incorrectly returns false from isUserInRole when user is authenticated

by arjan tijms (JIRA)

arjan tijms created WFLY-2854: --------------------------------- Summary: '**' role incorrectly returns false from isUserInRole when user is authenticated Key: WFLY-2854 URL: https://issues.jboss.org/browse/WFLY-2854 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: 8.0.0.CR1 Reporter: arjan tijms Assignee: Darran Lofthouse When authentication has taken place in a web application such that {{HttpServletRequest#getUserprincipap}} does not return null, testing for role '**' using {{HttpServletRequest#isUserInRole}} returns false. This is not correct. According to Servlet 13.3: {quote} {noformat} If the role-name of the security-role to be tested is “**”, and the application has NOT declared an application security-role with role-name “**”, isUserInRole must only return true if the user has been authenticated; {noformat} {quote} This is demonstrated by the following test: https://github.com/arjantijms/javaee7-samples/blob/master/jacc/contexts/s... -- 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, 2 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 January 2014