jboss-jira February 2014

jboss-jira@lists.jboss.org

1 participants
2055 discussions

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

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2854?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-2854: --------------------------------- Component/s: Web (Undertow) > '**' 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, Web (Undertow) > Affects Versions: 8.0.0.CR1 > Reporter: arjan tijms > Assignee: Stuart Douglas > 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

10 years, 7 months

1
0
0 / 0

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

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2854?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-2854: ------------------------------------ Assignee: Stuart Douglas (was: Darran Lofthouse) > '**' 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: Stuart Douglas > 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5088) Weblogic EJB Lookup fails from JBoss AS

by living lazer (JIRA)

[ https://issues.jboss.org/browse/AS7-5088?page=com.atlassian.jira.plugin.s... ] living lazer commented on AS7-5088: ----------------------------------- Was this moved to a forum? I am facing the same issue, no idea and already spent 24hours... > Weblogic EJB Lookup fails from JBoss AS > ---------------------------------------- > > Key: AS7-5088 > URL: https://issues.jboss.org/browse/AS7-5088 > Project: Application Server 7 > Issue Type: Bug > Environment: JBoss AS 7.1.0.Final > EJB Deployed in Weblogic 10 > OS - Windows XP > JDK - jdk160_05 (Used by jboss) > Reporter: Badal Pradhan > > I am trying to access EJB deployed in Weblogic 10 by its RemoteInterface from JBoss. > My initial context config for lookup is as below: > Hashtable<String,String> wlContextEnv = new Hashtable<String,String>(); > wlContextEnv.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); > wlContextEnv.put(Context.PROVIDER_URL, "t3://localhost:7001"); > wlInitialContext = new InitialContext(wlContextEnv); > During access the bean it throws the below exception: > java.lang.LinkageError: Failed to link weblogic/corba/client/cluster/ORBSocketFactory > ..... > Caused by: java.lang.ClassNotFoundException: com.sun.corba.se.spi.legacy.connection.ORBSocketFactory > Since the above class belongs to jdk rt.jar then what is the issue here? Am I missed any config for it. > Note: I have wlclient.jar in my ear/lib. -- 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] (DROOLS-319) "Unknown boolean operator" RuntimeException

by David Tombs (JIRA)

[ https://issues.jboss.org/browse/DROOLS-319?page=com.atlassian.jira.plugin... ] David Tombs commented on DROOLS-319: ------------------------------------ Hi Michael, I don't remember exactly how I did it but somewhere on the stacktrace from the exception I saw which constraint it was evaluating. Hope that helps. > "Unknown boolean operator" RuntimeException > ------------------------------------------- > > Key: DROOLS-319 > URL: https://issues.jboss.org/browse/DROOLS-319 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Windows 8, java version "1.7.0_40" > Reporter: David Tombs > Assignee: Mark Proctor > > Steps to reproduce: > # Create a decision table with something like {{fooString != ""}} in the constraint and {{true}} in the rule cell. > # Execute the rule against a few objects. > Actual Result: > An internal Drools thread will crash with {{java.lang.RuntimeException: Unknown boolean operator}} when trying to compile {{fooString != "" == true}}. > {noformat} > Exception in thread "Thread-15" java.lang.RuntimeException: Unknown boolean operator > at org.drools.rule.constraint.ConditionAnalyzer$AritmeticOperator.fromMvelOpCode(ConditionAnalyzer.java:1059) > at org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:169) > at org.drools.rule.constraint.ConditionAnalyzer.analyzeSingleCondition(ConditionAnalyzer.java:106) > at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:99) > at org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:70) > at org.drools.rule.constraint.MvelConditionEvaluator.getAnalyzedCondition(MvelConditionEvaluator.java:83) > at org.drools.rule.constraint.MvelConstraint.executeJitting(MvelConstraint.java:270) > at org.drools.rule.constraint.MvelConstraint.access$200(MvelConstraint.java:51) > at org.drools.rule.constraint.MvelConstraint$ConditionJitter.run(MvelConstraint.java:250) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > {noformat} > Expected Result: > Even if an Exception is thrown, the currently-thrown exception is too low level and took me lots of investigation and debugging inside the drools code to figure out what I did wrong. -- 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-1168) MDB is looking up UserTransaction even if it isn't Bean Managed

by Gus Gu (JIRA)

[ https://issues.jboss.org/browse/WFLY-1168?page=com.atlassian.jira.plugin.... ] Gus Gu commented on WFLY-1168: ------------------------------ Will this fix be deployed in WildFly 8 final? I got the exception when I run seam 2.3 app and WildFly 8 CR1. Thanks!! > MDB is looking up UserTransaction even if it isn't Bean Managed > --------------------------------------------------------------- > > Key: WFLY-1168 > URL: https://issues.jboss.org/browse/WFLY-1168 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Stefano Maestri > Assignee: Eduardo Martins > > Investigating on a use case I've seen that MDB comes to org.jboss.jca.adapters.jdbc.WrapperDataSource looking up for UT. It fails with this exception > javax.naming.NamingException: JBAS014237: Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction [Root exception is java.lang.IllegalStateException: JBAS014237: Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction] > the problem is exposed running > org.jboss.as.test.integration.ejb.mdb.MDBTestCase -- 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

← Newer
1
...
203
204
205
206
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2014