May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-136) RemotingConnector converts the AuthenticationContext to an anonymous context

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-136?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated REMJMX-136: ------------------------------------ Fix Version/s: 3.0.0.Beta4 > RemotingConnector converts the AuthenticationContext to an anonymous context > ---------------------------------------------------------------------------- > > Key: REMJMX-136 > URL: https://issues.jboss.org/browse/REMJMX-136 > Project: Remoting JMX > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Fix For: 3.0.0.Beta4 > > > If no {{CallbackHandler}} or no JMX credentials are defined the {{org.jboss.remotingjmx.RemotingConnector}} the {{AuthenticationContext}} is converted to an anonymous context. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-136) RemotingConnector converts the AuthenticationContext to an anonymous context

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-136?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-136. ------------------------------------- Resolution: Done > RemotingConnector converts the AuthenticationContext to an anonymous context > ---------------------------------------------------------------------------- > > Key: REMJMX-136 > URL: https://issues.jboss.org/browse/REMJMX-136 > Project: Remoting JMX > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Fix For: 3.0.0.Beta4 > > > If no {{CallbackHandler}} or no JMX credentials are defined the {{org.jboss.remotingjmx.RemotingConnector}} the {{AuthenticationContext}} is converted to an anonymous context. -- 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)

Darran Lofthouse created ELY-1169: ------------------------------------- Summary: 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] (ELY-1154) Update CredentialStore API to take Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1154?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1154. ----------------------------------- Resolution: Done > Update CredentialStore API to take Supplier<Provider[]> > ------------------------------------------------------- > > Key: ELY-1154 > URL: https://issues.jboss.org/browse/ELY-1154 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credential Store > 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] (ELY-1155) EJB client requires authentication context to be configured

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1155?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1155. ----------------------------------- Resolution: Done > EJB client requires authentication context to be configured > ----------------------------------------------------------- > > Key: ELY-1155 > URL: https://issues.jboss.org/browse/ELY-1155 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta42 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta43 > > > Lets have wildfly-config.xml: > {code:java} > <configuration> > <jboss-ejb-client xmlns="urn:jboss:wildfly-client-ejb:3.0"> > <connections> > <connection uri="remote+http://127.0.0.1:8080" /> > </connections> > </jboss-ejb-client> > </configuration> > {code} > EJB client requires authentication context to be configured and this will fail. > If I following lines are added, everything is fine. > {code:java} > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="default"/> > </authentication-rules> > <authentication-configurations> > <configuration name="default"> > <use-service-loader-providers/> > </configuration> > </authentication-configurations> > </authentication-client> > {code} > IMHO, this should not be required. > Here is a stacktrace. > {code:java} > 10:55:35,178 INFO [org.wildfly.security.Version:57] ELY00001: WildFly Elytron version 1.1.0.Beta42-redhat-1 > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:49) > at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:282) > at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:81) > at org.jboss.remoting3.Endpoint.getConnectedIdentity(Endpoint.java:139) > at org.jboss.remoting3.Endpoint.getConnection(Endpoint.java:216) > at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider.lambda$discover$0(RemotingEJBDiscoveryProvider.java:103) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider.discover(RemotingEJBDiscoveryProvider.java:103) > at org.wildfly.discovery.impl.AggregateDiscoveryProvider.discover(AggregateDiscoveryProvider.java:58) > at org.wildfly.discovery.ConfiguredProvider.discover(ConfiguredProvider.java:45) > at org.wildfly.discovery.Discovery.discover(Discovery.java:94) > at org.jboss.ejb.client.EJBClientContext.discover(EJBClientContext.java:442) > at org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:714) > at org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:701) > at org.jboss.ejb.client.EJBClientContext.createSession(EJBClientContext.java:681) > at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:288) > at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:146) > at org.wildfly.naming.client.AbstractContext.lookup(AbstractContext.java:88) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:153) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at client.Client.main(Client.java:48) > Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: CONF0003: Unexpected end of document > at file:/home/istraka/repositories/istraka/mock-artifacts/ejbclient/eap7.1-set-source-ip-address/client/target/classes/META-INF/wildfly-config.xml:23:17 > at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40) > at java.security.AccessController.doPrivileged(Native Method) > at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36) > ... 21 more > Caused by: org.wildfly.client.config.ConfigXMLParseException: CONF0003: Unexpected end of document > at file:/home/istraka/repositories/istraka/mock-artifacts/ejbclient/eap7.1-set-source-ip-address/client/target/classes/META-INF/wildfly-config.xml:23:17 > at org.wildfly.client.config.ConfigurationXMLStreamReader.unexpectedDocumentEnd(ConfigurationXMLStreamReader.java:266) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:208) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:141) > at org.wildfly.se > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-773) Where AuthenticationConfiguration has calls to PasswordFactory.getInstance(alg) pass in Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-773?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-773. ---------------------------------- Resolution: Done > Where AuthenticationConfiguration has calls to PasswordFactory.getInstance(alg) pass in Supplier<Provider[]> > ------------------------------------------------------------------------------------------------------------ > > Key: ELY-773 > URL: https://issues.jboss.org/browse/ELY-773 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > This may be obsoleted by ongoing work but just wanted an issue to track where AuthenticationConfiguration and related classes currently uses PaswordFactory.getInstance without passing in a Supplier for Provider[]. > * SetCredentialsConfiguration > * SetKeyStoreCredentialAuthenticationConfiguration > * ElytronAuthenticator > * ElytronXmlParser. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-837) Clean up provider usage and definition in XML config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-837?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-837. ---------------------------------- Resolution: Done > Clean up provider usage and definition in XML config > ---------------------------------------------------- > > Key: ELY-837 > URL: https://issues.jboss.org/browse/ELY-837 > Project: WildFly Elytron > Issue Type: Task > Components: XML > Reporter: David Lloyd > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > We are very inconsistent about how we're defining and using providers in the XML configuration. We need to meet the following requirements: > * Provide a single top-level element from the substitution group {{abstract-providers}} that specifies the providers to use in the absence of any other configuration; default to {{use-system-providers}} > * Update the following types (or appropriate enclosing type) to accept an optional nested {{abstract-providers}} override: > ** {{key-store-type}} > ** {{credential-store-type}} > ** {{hashed-password-type}} > * Update the following types to use an optional {{provider}} *attribute* (not nested element) to allow selection of a specific provider: > ** {{credential-store-type}} > ** {{key-store-type}} -- already done! > ** {{hashed-password-type}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1158) Make JBoss Local User quiet by default.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1158?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1158. ----------------------------------- Resolution: Done > Make JBoss Local User quiet by default. > --------------------------------------- > > Key: ELY-1158 > URL: https://issues.jboss.org/browse/ELY-1158 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > This mechanism in all management cases has previously been hard coded to be quiet by default, the is the predominant usage of the mechanism. > For a couple of EJB edge cases which have been found in the test suite we are putting in a lot of effort to keep it interactive by default. > If we don't make it quiet by default we are going to require either a wildfly-config.xml for each management client which is something we are trying to avoid or each management client is going to require access to the mechanism properties from the authentication configuration so they can be safely manipulated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1163) Impossible to override mechanism properties in authentication configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1163?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1163. ----------------------------------- Resolution: Done > Impossible to override mechanism properties in authentication configuration > --------------------------------------------------------------------------- > > Key: ELY-1163 > URL: https://issues.jboss.org/browse/ELY-1163 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > Once a value has been specified for a mechanism property it is impossible to override it -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1132) Unable to load passwords from wildfly-config.xml

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1132?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1132. ----------------------------------- Resolution: Done > Unable to load passwords from wildfly-config.xml > ------------------------------------------------ > > Key: ELY-1132 > URL: https://issues.jboss.org/browse/ELY-1132 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta43 > > > I see the following exception, adding use-service-loader-providers does not help > Caused by: java.security.NoSuchAlgorithmException: ELY08028: Invalid algorithm "clear" > at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseClearPassword$47(ElytronXmlParser.java:2009) > ... 46 more > Looks like this should just be hard coded to use the Elytron provider? -- 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