June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1067) Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1067?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1067: ---------------------------------- Fix Version/s: 1.1.0.CR2 (was: 1.1.0.CR1) > Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML > -------------------------------------------------------------------------------------------------- > > Key: ELY-1067 > URL: https://issues.jboss.org/browse/ELY-1067 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1031) Make the CredentialStore class final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1031?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1031: ---------------------------------- Fix Version/s: 1.1.0.CR2 (was: 1.1.0.CR1) > Make the CredentialStore class final > ------------------------------------ > > Key: ELY-1031 > URL: https://issues.jboss.org/browse/ELY-1031 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credential Store > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Priority: Critical > Fix For: 1.1.0.CR2 > > > Unless there is a reason this has not already be done the class should probably be made final to be sure extension is not possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-969) Add a KeyStore implementation that can use the key store password for retrieving entries.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-969?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-969: --------------------------------- Fix Version/s: 1.1.0.CR2 (was: 1.1.0.CR1) > Add a KeyStore implementation that can use the key store password for retrieving entries. > ----------------------------------------------------------------------------------------- > > Key: ELY-969 > URL: https://issues.jboss.org/browse/ELY-969 > Project: WildFly Elytron > Issue Type: Feature Request > Components: KeyStores > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.CR2 > > > A KeyManager which uses a KeyStore is defined independently of the KeyStore - it is the KeyManager that has the password for the entry in the KeyStore whilst the KeyStore has the password for the overall store. > In many cases the password used for the overall store is the same password as used for the entries. > We should provide a KeyStore implementation that can substitute the password received. > We may even be able to go one step further and add a password resolver which could mean a CredentialStore is used to obtain the password for different entries, -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1270) Release WildFly Elytron 1.1.0.CR1

by Darran Lofthouse (JIRA)

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

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6590) Client thread pool max size parameter should be possible to parametrize in CLI

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6590?page=com.atlassian.jira.plugin.... ] Jeff Mesnil closed WFLY-6590. ----------------------------- Resolution: Duplicate Issue > Client thread pool max size parameter should be possible to parametrize in CLI > ------------------------------------------------------------------------------ > > Key: WFLY-6590 > URL: https://issues.jboss.org/browse/WFLY-6590 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > > Based on discussion in JBEAP-2947, we should provide CLI parameter to set maximum size of client thread pool. > Currently {{-Dactivemq.artemis.client.global.thread.pool.max.size=<value>}} must be provided as system property during start of EAP 7 server. > This thread pool can be injected by Wildfly. This could be the way to limit make its size configurable by Wildfly -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1271) Elytron server-ssl-context should not use default value when referenced security-domain cannot be used

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1271?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1271: ------------------------------ Affects Version/s: 1.1.0.Beta52 > Elytron server-ssl-context should not use default value when referenced security-domain cannot be used > ------------------------------------------------------------------------------------------------------ > > Key: ELY-1271 > URL: https://issues.jboss.org/browse/ELY-1271 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta52 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > When {{security-domain}} from {{server-ssl-context}} cannot verify {{X509PeerCertificateChainEvidence}} then {{server-ssl-context}} should rather fail then use some default for {{X509TrustManager}} in [1]. It causes that misconfiguration in security domain is masked. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/656354343e7e28fd... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1271) Elytron server-ssl-context does not use default value when referenced security-domain cannot be used

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1271: --------------------------------- Summary: Elytron server-ssl-context does not use default value when referenced security-domain cannot be used Key: ELY-1271 URL: https://issues.jboss.org/browse/ELY-1271 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical When {{security-domain}} from {{server-ssl-context}} cannot verify {{X509PeerCertificateChainEvidence}} then {{server-ssl-context}} should rather fail then use some default for {{X509TrustManager}} in [1]. It causes that misconfiguration in security domain is masked. [1] https://github.com/wildfly-security/wildfly-elytron/blob/656354343e7e28fd... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1271) Elytron server-ssl-context should not use default value when referenced security-domain cannot be used

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1271?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1271: ------------------------------ Summary: Elytron server-ssl-context should not use default value when referenced security-domain cannot be used (was: Elytron server-ssl-context does not use default value when referenced security-domain cannot be used) > Elytron server-ssl-context should not use default value when referenced security-domain cannot be used > ------------------------------------------------------------------------------------------------------ > > Key: ELY-1271 > URL: https://issues.jboss.org/browse/ELY-1271 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > When {{security-domain}} from {{server-ssl-context}} cannot verify {{X509PeerCertificateChainEvidence}} then {{server-ssl-context}} should rather fail then use some default for {{X509TrustManager}} in [1]. It causes that misconfiguration in security domain is masked. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/656354343e7e28fd... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3030) Upgrade WildFly Elytron to 1.1.0.CR1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3030?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-11866 to WFCORE-3030: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3030 (was: JBEAP-11866) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade WildFly Elytron to 1.1.0.CR1 > ------------------------------------ > > Key: WFCORE-3030 > URL: https://issues.jboss.org/browse/WFCORE-3030 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1270) Release WildFly Elytron 1.1.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1270: ------------------------------------- Summary: Release WildFly Elytron 1.1.0.CR1 Key: ELY-1270 URL: https://issues.jboss.org/browse/ELY-1270 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta56 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017