September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1362) NullPointerException if Thread.getContextClassLoader() returns null

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1362?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1362: ---------------------------------- Description: We just need to detect the null class loader and return null. Also ElytronXmlParser assumes it is always available. was:We just need to detect the null class loader and return null. > NullPointerException if Thread.getContextClassLoader() returns null > ------------------------------------------------------------------- > > Key: ELY-1362 > URL: https://issues.jboss.org/browse/ELY-1362 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta3 > > > We just need to detect the null class loader and return null. > Also ElytronXmlParser assumes it is always available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9337) servlet container has no UTF-8 encoding default set, produces garbage on form submissions

by Mr Gruust (JIRA)

Mr Gruust created WFLY-9337: ------------------------------- Summary: servlet container has no UTF-8 encoding default set, produces garbage on form submissions Key: WFLY-9337 URL: https://issues.jboss.org/browse/WFLY-9337 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 11.0.0.CR1 Reporter: Mr Gruust Assignee: Jason Greene The problem described over there https://stackoverflow.com/questions/31205287/encoding-servlets-with-utf-8... still exists with the latest release. I had to explicitly set UTF-8 as default encoding to make resteasy properly decode form submissions and not decode UTF-8 as latin-1 (at least it looks a lot like that to me). On top of that, persisting session ids to file store (without using <distributable/> in web.xml) tends to lose the session store when reloading the webapp too fast. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1362) NullPointerException if Thread.getContextClassLoader() returns null

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1362: ------------------------------------- Summary: NullPointerException if Thread.getContextClassLoader() returns null Key: ELY-1362 URL: https://issues.jboss.org/browse/ELY-1362 Project: WildFly Elytron Issue Type: Bug Components: API / SPI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta3 We just need to detect the null class loader and return null. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9240) WeldSecurityServices not able to obtain the current SecurityDomain anymore

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-9240: ---------------------------------------- Investigating this I am seeing some slightly different behaviour than the description, after running the test I am seeing the following stack trace in the logs: - {noformat} Caused by: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) at org.wildfly.security.auth.server.SecurityDomain.getCurrent(SecurityDomain.java:171) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:74) at org.jboss.weld.tests.event.async.context.security.Printer$$$view2.print(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {noformat} This does indicate I have a bug within Elytron I need to fix but that will not be the solution to the current failure. The NullPointerException I am seeing is because Thread.getContextClassLoader() is returning null so for some reason the deployments class loader is not associated with the Thread. I will apply a fix to WildFly Elytron 1.2 which will detect the null ClassLoader and return null from the SecurityDomain.getCurrent, for the purpose of this specifically failing test I think investigation needs to look into why the class loader is not set for the thread during the test. > WeldSecurityServices not able to obtain the current SecurityDomain anymore > -------------------------------------------------------------------------- > > Key: WFLY-9240 > URL: https://issues.jboss.org/browse/WFLY-9240 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Affects Versions: 11.0.0.Beta1, 11.0.0.CR1 > Reporter: Martin Kouba > Assignee: Darran Lofthouse > Priority: Critical > > The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore. > The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}. > Note that this worked on WildFly *11.0.0.Alpha1*. > It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9336) Extend security context propagation test coverage

by Josef Cacek (JIRA)

Josef Cacek created WFLY-9336: --------------------------------- Summary: Extend security context propagation test coverage Key: WFLY-9336 URL: https://issues.jboss.org/browse/WFLY-9336 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Josef Cacek Priority: Critical Extend security context propagation test coverage: * add servlet-to-ejb credential propagation scenarios (BASIC, FORM, BEARER) * add tests for manual credentials retrieving (use in *-to-servlet scenarios) * credential-less propagation -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9336) Extend security context propagation test coverage

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-9336?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-9336: --------------------------------- Assignee: Josef Cacek > Extend security context propagation test coverage > ------------------------------------------------- > > Key: WFLY-9336 > URL: https://issues.jboss.org/browse/WFLY-9336 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Critical > > Extend security context propagation test coverage: > * add servlet-to-ejb credential propagation scenarios (BASIC, FORM, BEARER) > * add tests for manual credentials retrieving (use in *-to-servlet scenarios) > * credential-less propagation -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9240) WeldSecurityServices not able to obtain the current SecurityDomain anymore

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-9240: ------------------------------------ [~dlofthouse] No, since EAP 7.1 is using Weld 2.4 and this issue is only reproducible with Weld 3 (CDI 2). > WeldSecurityServices not able to obtain the current SecurityDomain anymore > -------------------------------------------------------------------------- > > Key: WFLY-9240 > URL: https://issues.jboss.org/browse/WFLY-9240 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Affects Versions: 11.0.0.Beta1, 11.0.0.CR1 > Reporter: Martin Kouba > Assignee: Darran Lofthouse > Priority: Critical > > The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore. > The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}. > Note that this worked on WildFly *11.0.0.Alpha1*. > It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9335) Remove ignored tests org.wildfly.test.integration.security.picketlink.idm.*

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-9335: ---------------------------------- Summary: Remove ignored tests org.wildfly.test.integration.security.picketlink.idm.* Key: WFLY-9335 URL: https://issues.jboss.org/browse/WFLY-9335 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Hynek Švábek Priority: Minor Remove ignored tests org.wildfly.test.integration.security.picketlink.idm.* -> PicketLink IDM is unsupported in EAP and PicketLink will be removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9334) Fix CredentialStoreTestCase

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-9334: ---------------------------------- Summary: Fix CredentialStoreTestCase Key: WFLY-9334 URL: https://issues.jboss.org/browse/WFLY-9334 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Hynek Švábek Priority: Minor . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9333) Fix/unignore ConstantPrincipalDecoderTestCase

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-9333: ---------------------------------- Summary: Fix/unignore ConstantPrincipalDecoderTestCase Key: WFLY-9333 URL: https://issues.jboss.org/browse/WFLY-9333 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Hynek Švábek Priority: Minor . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 2017