August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-747) SubjectInfo.getRoles is null with cached credentials in SPNEGO

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-747?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-747: ----------------------------------------- Assignee: (was: Darran Lofthouse) > SubjectInfo.getRoles is null with cached credentials in SPNEGO > -------------------------------------------------------------- > > Key: SECURITY-747 > URL: https://issues.jboss.org/browse/SECURITY-747 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Environment: EAP 6.1 > SPNEGO setup with KERBEROS > Reporter: Chris Dolphy > > SecurityContextAssociation.getSecurityContext().getSubjectInfo().getRoles() returns the user's roles on the initial login, but if you refresh you get null. All subsequent calls will return null. > I'm using the 3rd test in JBoss Negotiation Toolkit. If you refresh after logging in, you get a NullPointerException > It appears that with Basic autentication, JBossWebRealm.authenticate calls > JBossAuthenticationManager.getSubjectRoles > which sets the roles on the SubjectInfo. However, with SPNEGO > (NegotiationAuthenticator) JBossWebRealm.authenticate is not called on > subsequent requests due to request.getUserPrincipal() being set, so the roles are never set on SubjectInfo. However, the role information is in SubjectInfo as a principal. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1650) Automatic detection of file based KeyStore types.

by Martin Mazanek (JIRA)

Martin Mazanek created ELY-1650: ----------------------------------- Summary: Automatic detection of file based KeyStore types. Key: ELY-1650 URL: https://issues.jboss.org/browse/ELY-1650 Project: WildFly Elytron Issue Type: Enhancement Reporter: Martin Mazanek Assignee: Martin Mazanek -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3416) NPE in Undertow Extension if login module doesn't set Principal

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3416?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-3416: -------------------------------------- Assignee: (was: Darran Lofthouse) > NPE in Undertow Extension if login module doesn't set Principal > --------------------------------------------------------------- > > Key: WFLY-3416 > URL: https://issues.jboss.org/browse/WFLY-3416 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.CR2 > Reporter: Josef Cacek > > NPE is thrown during authentication if a LoginModule doesn't set any principal to the Subject. > The problem comes from {{org.wildfly.extension.undertow.security.AccountImpl}} constructor call {{principal.getName()}}. > {code} > Caused by: java.lang.NullPointerException > at org.wildfly.extension.undertow.security.AccountImpl.<init>(AccountImpl.java:61) > at org.wildfly.extension.undertow.security.JAASIdentityManagerImpl.verifyCredential(JAASIdentityManagerImpl.java:123) > ... > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-733) Session replication broken by NegotiationAuthenticator valve

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-733?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-733: ----------------------------------------- Assignee: (was: Darran Lofthouse) > Session replication broken by NegotiationAuthenticator valve > ------------------------------------------------------------ > > Key: SECURITY-733 > URL: https://issues.jboss.org/browse/SECURITY-733 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_2_2_2 > Reporter: Darran Lofthouse > > From an initial review of the code I believe this is because the ClusterSessionValve implements the Listener interface - however the wrapper class does not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-733) Session replication broken by NegotiationAuthenticator valve

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-733?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-733: -------------------------------------- Fix Version/s: (was: Negotiation_2_2_3) > Session replication broken by NegotiationAuthenticator valve > ------------------------------------------------------------ > > Key: SECURITY-733 > URL: https://issues.jboss.org/browse/SECURITY-733 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_2_2_2 > Reporter: Darran Lofthouse > > From an initial review of the code I believe this is because the ClusterSessionValve implements the Listener interface - however the wrapper class does not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2036) Review of AbstractControllerTestBase

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2036?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-2036: -------------------------------------- Assignee: (was: Darran Lofthouse) > Review of AbstractControllerTestBase > ------------------------------------ > > Key: WFLY-2036 > URL: https://issues.jboss.org/browse/WFLY-2036 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 8.0.0.Alpha4 > Reporter: Darran Lofthouse > Fix For: Awaiting Volunteers > > > Currently we have the abstract class AbstractControllerTestBase to use as the base for simplified controller testing, however due to visibility problems we now have three versions of this class which have also started to diverge slightly. > Before this goes too far we should try and bring this back down to one. Extensions of this class also have certain amount of common functionality. > Maybe also work converting some of this to a 'org.junit.runner.Runner' to avoid the need for inheritance, additional annotations can then be used to define how to configure the controller being tested. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-97) Optimise addNotificationListener so no handback needs to be sent.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-97?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned REMJMX-97: -------------------------------------- Assignee: (was: Darran Lofthouse) > Optimise addNotificationListener so no handback needs to be sent. > ----------------------------------------------------------------- > > Key: REMJMX-97 > URL: https://issues.jboss.org/browse/REMJMX-97 > Project: Remoting JMX > Issue Type: Sub-task > Components: Connection > Reporter: Darran Lofthouse > Fix For: 2.0.2.CR1 > > > The following method call has been updated as a result of REMJMX-91 so null is sent for the handback - this is to retain compatibility with existing installations currently using version 2 of the protocol. > {code} > public void addNotificationListener(final ObjectName name, NotificationListener listener, > final NotificationFilter filter, final Object handback) throws InstanceNotFoundException, IOException { > {code} > In version 3 we can drop sending the handle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-96) Create version 3 of the protocol

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-96?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned REMJMX-96: -------------------------------------- Assignee: (was: Darran Lofthouse) > Create version 3 of the protocol > -------------------------------- > > Key: REMJMX-96 > URL: https://issues.jboss.org/browse/REMJMX-96 > Project: Remoting JMX > Issue Type: Task > Reporter: Darran Lofthouse > Fix For: 2.0.2.CR1 > > > This is not a commitment to add version 3, that will be determined by the impact of other changes made. > This is more a case of tracking the changes that will need to be made in version 3 if it ever exists. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-81) Add http-remoting-jmx testing

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-81?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned REMJMX-81: -------------------------------------- Assignee: (was: Darran Lofthouse) > Add http-remoting-jmx testing > ----------------------------- > > Key: REMJMX-81 > URL: https://issues.jboss.org/browse/REMJMX-81 > Project: Remoting JMX > Issue Type: Task > Components: Tests > Reporter: Darran Lofthouse > > Connecting over HTTP is now the default mode for WildFly yet we have no testing of this within the Remoting JMX project itself. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-81) Add http-remoting-jmx testing

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-81?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-81: ----------------------------------- Fix Version/s: (was: 2.0.2.CR1) > Add http-remoting-jmx testing > ----------------------------- > > Key: REMJMX-81 > URL: https://issues.jboss.org/browse/REMJMX-81 > Project: Remoting JMX > Issue Type: Task > Components: Tests > Reporter: Darran Lofthouse > > Connecting over HTTP is now the default mode for WildFly yet we have no testing of this within the Remoting JMX project itself. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018