May 2017 - jboss-jira - Jboss List Archives

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

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1132?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1132: ----------------------------------- I would say these are they: {code:java|title=ElytronXmlParser.java} case "key-store-clear-password": { // group 2 if (! gotSource || gotCredential) { throw reader.unexpectedElement(); } gotCredential = true; final char[] clearPassword = ((ClearPassword) parseClearPassword(reader, Security::getProviders).get()).getPassword(); passwordFactory = () -> clearPassword; break; } ... case "key-store-clear-password": { if (keyStoreCredential != null) throw reader.unexpectedElement(); ExceptionSupplier<Password, ConfigXMLParseException> credential = parseClearPassword(reader, Security::getProviders); keyStoreCredential = () -> new PasswordEntry(credential.get()); break; } ... case "protection-parameter-credentials": { if (++attributesSectionCount > 2) throw reader.unexpectedContent(); credentialSourceSupplier = parseCredentialsType(reader, keyStoresMap, credentialStoresMap, Security::getProviders); break; } {code} > 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 > > 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2139) Implement DNS-based PING

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/JGRP-2139?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated JGRP-2139: -------------------------------------- Fix Version/s: 4.0.2 > Implement DNS-based PING > ------------------------ > > Key: JGRP-2139 > URL: https://issues.jboss.org/browse/JGRP-2139 > Project: JGroups > Issue Type: Enhancement > Environment: * OpenShift and Kubernetes (service discovery is done using SRV records) > * Any other environment that use {{A}} or {{SRV}} DNS records > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 4.0.2 > > > DNS Discovery might be very useful in Cloud environments (such as Kubernetes or OpenShift). They expose Services (which act as Load Balancers and Clustered Virtual IPs for Pods (Docker Containers)) with DNS {{SRV}} entries using the following scheme: {{_port._proto.ENDPOINT.service.namespace.sv.cluster.local}} (see [this issue|https://github.com/kubernetes/kubernetes/issues/29420] for more information). > The implementation should also allow the following: > * Change the DNS Server address > * Change or override TTL values > * Change DNS record type (either {{A}} or {{SRV}} > ** If the record type is {{SRV}}, it should also allow parting port > The implementation might be based on Oracle DNS tutorial: http://docs.oracle.com/javase/7/docs/technotes/guides/jndi/jndi-dns.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

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

by Martin Choma (JIRA)

Martin Choma created ELY-1133: --------------------------------- Summary: Unable to load passwords from wildfly-config.xml Key: ELY-1133 URL: https://issues.jboss.org/browse/ELY-1133 Project: WildFly Elytron Issue Type: Bug Reporter: Martin Choma Assignee: Darran Lofthouse 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8703) add tests for JCA workmanager and security inflow using legacy security and elytron security domain

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFLY-8703?page=com.atlassian.jira.plugin.... ] Martin Simka reassigned WFLY-8703: ---------------------------------- Assignee: Martin Simka (was: Stefano Maestri) > add tests for JCA workmanager and security inflow using legacy security and elytron security domain > --------------------------------------------------------------------------------------------------- > > Key: WFLY-8703 > URL: https://issues.jboss.org/browse/WFLY-8703 > Project: WildFly > Issue Type: Enhancement > Components: JCA, Test Suite > Reporter: Martin Simka > Assignee: Martin Simka > > Add test for JCA workmanager and security inflow: > * using legacy security domain > * using Elytron security domain > * mixed scenario where RA is defined with Elytron security domain and WorkManager hasn't enabled Elytron integration (it defaults to legacy security integration) - it's not supported and deployment should fail > WFLY-8204 adds elytron-enabled attribute to workmanager configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8204) work-manager and distributed-workmanager need an Elytron-enabled flag

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFLY-8204?page=com.atlassian.jira.plugin.... ] Martin Simka reassigned WFLY-8204: ---------------------------------- Assignee: Martin Simka (was: Flavia Rainone) > work-manager and distributed-workmanager need an Elytron-enabled flag > --------------------------------------------------------------------- > > Key: WFLY-8204 > URL: https://issues.jboss.org/browse/WFLY-8204 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Stefano Maestri > Assignee: Martin Simka > Priority: Blocker > Labels: elytron_integration > Fix For: 11.0.0.Alpha1 > > > 2 RA using the same bootStrapContext and so the same WorkManager. First RA has ElytronEnabled==true, while the second one has ElytronEnabled==false. We have a problem in this line: > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > When second RA will be deployed it will find security integration set for elytron not according to its configuration. And, since this method is changing securityIntegration on a deployment it would be a problem every time we have mixed configuration w/ and w/o Ely. > I think we should have elytron-enabled parameter also in workmanager/default-workmanager in jca subsytem and a check (in the method linked above and/or maybe elsewhere...I need to double check) that RA w/ elytron-enabled use only workmanager w/ elytron-enabled and vice versa. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8204) work-manager and distributed-workmanager need an Elytron-enabled flag

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFLY-8204?page=com.atlassian.jira.plugin.... ] Martin Simka reassigned WFLY-8204: ---------------------------------- Assignee: Flavia Rainone (was: Martin Simka) > work-manager and distributed-workmanager need an Elytron-enabled flag > --------------------------------------------------------------------- > > Key: WFLY-8204 > URL: https://issues.jboss.org/browse/WFLY-8204 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Stefano Maestri > Assignee: Flavia Rainone > Priority: Blocker > Labels: elytron_integration > Fix For: 11.0.0.Alpha1 > > > 2 RA using the same bootStrapContext and so the same WorkManager. First RA has ElytronEnabled==true, while the second one has ElytronEnabled==false. We have a problem in this line: > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > When second RA will be deployed it will find security integration set for elytron not according to its configuration. And, since this method is changing securityIntegration on a deployment it would be a problem every time we have mixed configuration w/ and w/o Ely. > I think we should have elytron-enabled parameter also in workmanager/default-workmanager in jca subsytem and a check (in the method linked above and/or maybe elsewhere...I need to double check) that RA w/ elytron-enabled use only workmanager w/ elytron-enabled and vice versa. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8703) add tests for JCA workmanager and security inflow using legacy security and elytron security domain

by Martin Simka (JIRA)

Martin Simka created WFLY-8703: ---------------------------------- Summary: add tests for JCA workmanager and security inflow using legacy security and elytron security domain Key: WFLY-8703 URL: https://issues.jboss.org/browse/WFLY-8703 Project: WildFly Issue Type: Enhancement Components: JCA, Test Suite Reporter: Martin Simka Assignee: Stefano Maestri Add test for JCA workmanager and security inflow: * using legacy security domain * using Elytron security domain * mixed scenario where RA is defined with Elytron security domain and WorkManager hasn't enabled Elytron integration (it defaults to legacy security integration) - it's not supported and deployment should fail WFLY-8204 adds elytron-enabled attribute to workmanager configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8704) add tests for JCA workmanager and security inflow using legacy security and elytron security domain

by Martin Simka (JIRA)

Martin Simka created WFLY-8704: ---------------------------------- Summary: add tests for JCA workmanager and security inflow using legacy security and elytron security domain Key: WFLY-8704 URL: https://issues.jboss.org/browse/WFLY-8704 Project: WildFly Issue Type: Enhancement Components: JCA, Test Suite Reporter: Martin Simka Assignee: Stefano Maestri Add test for JCA workmanager and security inflow: * using legacy security domain * using Elytron security domain * mixed scenario where RA is defined with Elytron security domain and WorkManager hasn't enabled Elytron integration (it defaults to legacy security integration) - it's not supported and deployment should fail WFLY-8204 adds elytron-enabled attribute to workmanager configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8693) @Resource not working on Dynamic Servlets

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/WFLY-8693?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on WFLY-8693: ------------------------------------- I took a glance at this and I think it would make sense if it behaved equally to static servlets in this regard - e.g. if the injection should work. The specification (3.1 servlet spec, section 4.4.3.5) mentions something along these lines, although it's blurred as they use inappropriate wording - from CDI standpoints, servlet cannot be a managed bean, instead it's non contextual instance. Implementation-wise, I did some digging as well, but came up empty handed. All I know is that Weld subsystem does *not* provide the injection for static servlets as can be seen in [{{InjectionTargets}}|https://github.com/wildfly/wildfly/blob/master/weld/subsystem/src/main/java/org/jboss/as/weld/injection/InjectionTargets.java#L81]. It in fact skips it on purpose (btw it can be set here which will make it work, but finding out if the class is a dynamic servlet is messy at best). Perhaps [~swd847] can provide some directions. > @Resource not working on Dynamic Servlets > ----------------------------------------- > > Key: WFLY-8693 > URL: https://issues.jboss.org/browse/WFLY-8693 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Dan Siviter > > When a dynamic servlet is used then {{@Resource}} does not work. When using {{@WebServlet}} it does inject fine and only appears to be associated with dynamic ones. Test used {{ManagedExecutorService}} but it may apply to more. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2765) CLI, add module with directories as resources

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2765: -------------------------------------------- Summary: CLI, add module with directories as resources Key: WFCORE-2765 URL: https://issues.jboss.org/browse/WFCORE-2765 Project: WildFly Core Issue Type: Feature Request Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Ability to copy directories, ability to create new directories for non existing directories. In order to not break existing behaviour (failure if a resource doesn't exist), a new option should be introduced to disable check of non existing resource, -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2017