August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-915) Migrate MessageFactory discovery to use ServiceLoader

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-915?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-915: ----------------------------------------- Assignee: (was: Darran Lofthouse) > Migrate MessageFactory discovery to use ServiceLoader > ----------------------------------------------------- > > Key: SECURITY-915 > URL: https://issues.jboss.org/browse/SECURITY-915 > Project: PicketBox > Issue Type: Feature Request > Components: Negotiation > Reporter: Darran Lofthouse > > At the moment we have statically defined class names and attempt to load them in turn to identify which ones are actually available - ServiceLoader based discovery would eliminate this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-915) Migrate MessageFactory discovery to use ServiceLoader

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-915?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-915: -------------------------------------- Fix Version/s: (was: Negotiation_3_0_5_CR1) > Migrate MessageFactory discovery to use ServiceLoader > ----------------------------------------------------- > > Key: SECURITY-915 > URL: https://issues.jboss.org/browse/SECURITY-915 > Project: PicketBox > Issue Type: Feature Request > Components: Negotiation > Reporter: Darran Lofthouse > > At the moment we have statically defined class names and attempt to load them in turn to identify which ones are actually available - ServiceLoader based discovery would eliminate this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-943) AdvancedLdapLoginModule authentication fails when some part of DN is part of LDAP URL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-943?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-943: ----------------------------------------- Assignee: (was: Darran Lofthouse) > AdvancedLdapLoginModule authentication fails when some part of DN is part of LDAP URL > ------------------------------------------------------------------------------------- > > Key: SECURITY-943 > URL: https://issues.jboss.org/browse/SECURITY-943 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_3_0_2_Final > Reporter: Ondrej Lukas > > In case when part of DN is placed in LDAP URL instead of baseCtxDN then authentication fails (see [1] for details about this URL) in AdvancedLdapLoginModule. Authentication is provided by binding with user DN and password, but in this case user DN does not include DN part from LDAP URL which leads to fail. > Thrown exception: > {code} > javax.naming.AuthenticationException: LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=jduke,ou=People > com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3135) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3081) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) > com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) > com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) > com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) > com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) > org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114) > org.jboss.as.naming.InitialContext.init(InitialContext.java:99) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89) > org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43) > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) > javax.naming.InitialContext.init(InitialContext.java:244) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.security.negotiation.AdvancedLdapLoginModule.constructLdapContext(AdvancedLdapLoginModule.java:486) > org.jboss.security.negotiation.AdvancedLdapLoginModule.authenticate(AdvancedLdapLoginModule.java:669) > org.jboss.security.negotiation.AdvancedLdapLoginModule.innerLogin(AdvancedLdapLoginModule.java:397) > org.jboss.security.negotiation.AdvancedLdapLoginModule$AuthorizeAction.run(AdvancedLdapLoginModule.java:967) > org.jboss.security.negotiation.AdvancedLdapLoginModule.login(AdvancedLdapLoginModule.java:326) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ... > {code} > [1] https://tools.ietf.org/html/rfc2255 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-943) AdvancedLdapLoginModule authentication fails when some part of DN is part of LDAP URL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-943?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-943: -------------------------------------- Fix Version/s: (was: Negotiation_3_0_5_CR1) > AdvancedLdapLoginModule authentication fails when some part of DN is part of LDAP URL > ------------------------------------------------------------------------------------- > > Key: SECURITY-943 > URL: https://issues.jboss.org/browse/SECURITY-943 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_3_0_2_Final > Reporter: Ondrej Lukas > > In case when part of DN is placed in LDAP URL instead of baseCtxDN then authentication fails (see [1] for details about this URL) in AdvancedLdapLoginModule. Authentication is provided by binding with user DN and password, but in this case user DN does not include DN part from LDAP URL which leads to fail. > Thrown exception: > {code} > javax.naming.AuthenticationException: LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=jduke,ou=People > com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3135) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3081) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) > com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) > com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) > com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) > com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) > org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114) > org.jboss.as.naming.InitialContext.init(InitialContext.java:99) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89) > org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43) > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) > javax.naming.InitialContext.init(InitialContext.java:244) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.security.negotiation.AdvancedLdapLoginModule.constructLdapContext(AdvancedLdapLoginModule.java:486) > org.jboss.security.negotiation.AdvancedLdapLoginModule.authenticate(AdvancedLdapLoginModule.java:669) > org.jboss.security.negotiation.AdvancedLdapLoginModule.innerLogin(AdvancedLdapLoginModule.java:397) > org.jboss.security.negotiation.AdvancedLdapLoginModule$AuthorizeAction.run(AdvancedLdapLoginModule.java:967) > org.jboss.security.negotiation.AdvancedLdapLoginModule.login(AdvancedLdapLoginModule.java:326) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ... > {code} > [1] https://tools.ietf.org/html/rfc2255 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-917) Remove setStatusCode call in NegotiationMechanism

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-917?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-917: ----------------------------------------- Assignee: (was: Darran Lofthouse) > Remove setStatusCode call in NegotiationMechanism > ------------------------------------------------- > > Key: SECURITY-917 > URL: https://issues.jboss.org/browse/SECURITY-917 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > > Once UNDERTOW-548 is resolved we can remove manually setting the status code ourselves. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-917) Remove setStatusCode call in NegotiationMechanism

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-917?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-917: -------------------------------------- Fix Version/s: (was: Negotiation_3_0_5_CR1) > Remove setStatusCode call in NegotiationMechanism > ------------------------------------------------- > > Key: SECURITY-917 > URL: https://issues.jboss.org/browse/SECURITY-917 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > > Once UNDERTOW-548 is resolved we can remove manually setting the status code ourselves. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2584) Domain Mode JMX access through the HostController

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2584?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-2584: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Domain Mode JMX access through the HostController > ------------------------------------------------- > > Key: WFCORE-2584 > URL: https://issues.jboss.org/browse/WFCORE-2584 > Project: WildFly Core > Issue Type: Feature Request > Components: JMX, Management, Remoting > Reporter: Darran Lofthouse > Labels: JMX, domain-mode, investigation_required > > This task is first to review if this should be considered. > At the moment access to JMX is provided through the remoting connector of each AS instance - this task is to consider if we should actually make it available through the host controller with the host controller acting as a proxy. > The main motivation being to separate management and app traffic. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-103) Remoting JMX closing Remoting Endpoint before all tasks complete

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-103?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned REMJMX-103: --------------------------------------- Assignee: (was: Darran Lofthouse) > Remoting JMX closing Remoting Endpoint before all tasks complete > ---------------------------------------------------------------- > > Key: REMJMX-103 > URL: https://issues.jboss.org/browse/REMJMX-103 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final > Reporter: Brad Maxwell > > Remoting JMX closing Remoting Endpoint before all tasks are complete resulting in: > {code} > 2015-03-29 05:00:54,513 TRACE [Collectd-Thread-33-of-150] org.jboss.remoting.endpoint: Allocated tick to 2 of endpoint "endpoint" <7d484721> (opened Connection to /127.0.0.1:9999) > 2015-03-29 05:00:54,528 TRACE [Remoting "endpoint" task-3] org.jboss.remoting.endpoint: Registered successful result org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication$2$1@2e963f96 > 2015-03-29 05:00:54,533 TRACE [Remoting "endpoint" read-1] org.jboss.remoting.endpoint: Resource closed count 00000001 of endpoint "endpoint" <4b03debc> (closed Remoting connection <4d713ca3>) > 2015-03-29 05:00:54,533 TRACE [Collectd-Thread-7-of-150] org.jboss.remoting.endpoint: Finished phase 1 shutdown of endpoint "endpoint" <4b03debc> > 2015-03-29 05:00:54,559 TRACE [Collectd-Thread-125-of-150] org.jboss.remoting.endpoint: Finished phase 1 shutdown of endpoint "endpoint" <268c16fa> > 2015-03-29 05:00:54,559 TRACE [Remoting "endpoint" read-1] org.jboss.remoting.endpoint: Resource closed count 00000001 of endpoint "endpoint" <268c16fa> (closed Remoting connection <4d94514f>) > 2015-03-29 05:00:54,562 TRACE [Remoting "endpoint" read-1] org.jboss.remoting.endpoint: Resource closed count 00000001 of endpoint "endpoint" <f8ae998> (closed Remoting connection <50aacf67>) > 2015-03-29 05:00:54,562 TRACE [Collectd-Thread-77-of-150] org.jboss.remoting.endpoint: Finished phase 1 shutdown of endpoint "endpoint" <f8ae998> > 2015-03-29 05:00:54,602 TRACE [Remoting "endpoint" read-1] org.jboss.remoting.endpoint: Resource closed count 00000001 of endpoint "endpoint" <5368a58f> (closed Remoting connection <3ee11848>) > 2015-03-29 05:00:54,602 TRACE [Collectd-Thread-27-of-150] org.jboss.remoting.endpoint: Finished phase 1 shutdown of endpoint "endpoint" <5368a58f> > 2015-03-29 09:51:32,488 ERROR [Remoting "endpoint" read-1] org.xnio.listener: A channel event listener threw an exception > java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication$1@513f87d4 rejected from org.xnio.XnioWorker$TaskPool@21ee98f8[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372) > at org.xnio.XnioWorker.execute(XnioWorker.java:572) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:671) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:607) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1414) Add configuration for nonce handling timeouts etc...

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1414?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1414: ------------------------------------- Assignee: (was: Darran Lofthouse) > Add configuration for nonce handling timeouts etc... > ---------------------------------------------------- > > Key: ELY-1414 > URL: https://issues.jboss.org/browse/ELY-1414 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1414) Add configuration for nonce handling timeouts etc...

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1414?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1414: ---------------------------------- Fix Version/s: (was: 1.1.8.CR1) > Add configuration for nonce handling timeouts etc... > ---------------------------------------------------- > > Key: ELY-1414 > URL: https://issues.jboss.org/browse/ELY-1414 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > -- 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