May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1030) Move TokenSecurityRealm to org.wildfly.security.auth.realm package

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1030?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1030: ---------------------------------- Fix Version/s: 1.1.0.Beta44 (was: 1.1.0.Beta37) > Move TokenSecurityRealm to org.wildfly.security.auth.realm package > ------------------------------------------------------------------ > > Key: ELY-1030 > URL: https://issues.jboss.org/browse/ELY-1030 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Assignee: Pedro Igor > Priority: Critical > Fix For: 1.1.0.Beta44 > > > The LDAP and JDBC realms have their own package as they have quite a few utility and configuration classes, the token realm only has one so I don't think we really need this one to be in it'own realm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1029) Support clients that provide an optional CallbackHandler

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1029?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1029: ---------------------------------- Fix Version/s: 1.1.0.Beta44 (was: 1.1.0.Beta37) > Support clients that provide an optional CallbackHandler > -------------------------------------------------------- > > Key: ELY-1029 > URL: https://issues.jboss.org/browse/ELY-1029 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta44 > > > Clients such as the WildFly CLI provide a CallbackHandler implementation in case it is needed and not as a sign that it must be used, i.e. the desired outcome is that if the information required can be obtained from the configuration then authentication proceeds without interaction with the end user. > Neither the CLI or the end user should be required to be fully aware of the underlying security configuration. > This is similar to web browser HTTP authentication where there is only an interaction with the user if actually required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1170: ---------------------------------- Fix Version/s: 1.1.0.Beta44 (was: 1.1.0.Beta43) > The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]> > ----------------------------------------------------------------------------------- > > Key: ELY-1170 > URL: https://issues.jboss.org/browse/ELY-1170 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta44 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2754) Propagate sasl-mechanism-selector to elytron subsystem

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2754?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-2754: --------------------------------- Priority: Blocker (was: Critical) > Propagate sasl-mechanism-selector to elytron subsystem > ------------------------------------------------------ > > Key: WFCORE-2754 > URL: https://issues.jboss.org/browse/WFCORE-2754 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta16 > Reporter: Martin Švehla > Priority: Blocker > > sasl-mechanism-selector was introduced to Elytron client configuration to allow whitelisting specific SASL mechanism in the client. See WFCORE-2615 for the discussion. > This element should be also propagated to Elytron subsystem so it's available server side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1169) Release WildFly Elytron 1.1.0.Beta43

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1169?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1169. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta43 > ------------------------------------ > > Key: ELY-1169 > URL: https://issues.jboss.org/browse/ELY-1169 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta43 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8801) Legacy EJB client dependency in wildfly-feature-pack breaks AS TS

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8801: --------------------------------- Summary: Legacy EJB client dependency in wildfly-feature-pack breaks AS TS Key: WFLY-8801 URL: https://issues.jboss.org/browse/WFLY-8801 Project: WildFly Issue Type: Bug Components: EJB, Test Suite Reporter: Josef Cacek Priority: Critical The new jboss-ejb-client-legacy dependency in wildfly-feature-pack POM breaks AS TS client tests. Users can hit this issue if they define dependencies using the feature-pack pom. {code:xml} <dependency> <groupId>org.wildfly</groupId> <artifactId>wildfly-feature-pack</artifactId> <type>pom</type> </dependency> {code} The testsuite/shared has a dependency on wildfly-feature-pack POM which newly introduces the legacy EJB client dependency. (https://github.com/wildfly/wildfly/pull/10061/files) It results in classpath issues. When I hit the issue in my test, the test prints just this exception and the testsuite run hangs forever: {code} Exception in thread "XNIO-1 task-14" java.lang.NoSuchMethodError: org.jboss.ejb.client.Affinity.forUri(Ljava/net/URI;)Lorg/jboss/ejb/client/Affinity; at org.jboss.ejb.protocol.remote.ProtocolV3ObjectResolver.<init>(ProtocolV3ObjectResolver.java:43) at org.jboss.ejb.protocol.remote.EJBMarshallingCompatibilityHelper.getObjectResolver(EJBMarshallingCompatibilityHelper.java:42) at org.wildfly.naming.client.remote.RemoteClientTransport$1.handleMessage(RemoteClientTransport.java:155) at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:434) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:897) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2825) Upgrade WildFly Elytron to 1.1.0.Beta43

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2825: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.1.0.Beta43 Key: WFCORE-2825 URL: https://issues.jboss.org/browse/WFCORE-2825 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta22 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1170: ------------------------------------- Summary: The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]> Key: ELY-1170 URL: https://issues.jboss.org/browse/ELY-1170 Project: WildFly Elytron Issue Type: Task Components: Authentication Client Reporter: Darran Lofthouse Priority: Critical Fix For: 1.1.0.Beta43 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-141) Release Remoting JMX 3.0.0.Beta4

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-141: --------------------------------------- Summary: Release Remoting JMX 3.0.0.Beta4 Key: REMJMX-141 URL: https://issues.jboss.org/browse/REMJMX-141 Project: Remoting JMX Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-140) Upgrade WildFly Elytron to 1.1.0.Beta43

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-140: --------------------------------------- Summary: Upgrade WildFly Elytron to 1.1.0.Beta43 Key: REMJMX-140 URL: https://issues.jboss.org/browse/REMJMX-140 Project: Remoting JMX Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 May 2017