October 2017 - jboss-jira - Jboss List Archives

[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 commented on ELY-1170: --------------------------------------- I don't follow the comment about sibling relations, the end result of these changes is ElytronXml has a default root provider definition, at the root of the config an alternative configuration can be defined that will apply to all children, and then all children that make use of the Providers in any way have an option to further override for their specific needs. The Elytron subsystem is independent of this - this is specifically about the XML parser. The TrustManager definition in the Elytron subsystem DOES have the ability to specify which Providers to use. In the OpenSSL example a suitable configuration would be service loader based discovery to get the OpenSSL Provider at the start of the list with the Global/System providers second so that is completely achievable. If we really had a demonstratable issue with sharing the definition on the SSLContext we could add a further child element on the <trust-manager /> element but TBH we would always inherit from it's parent which is the SSLContext. > 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 > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

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

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Martin Choma edited comment on ELY-1170 at 10/18/17 7:00 AM: ------------------------------------------------------------- I am not sure if this is good feature or not. As I understand this allows inherit parents element provider - if specified on parent. These are my thoughts: * Consistency ** same feature is on sibling relation ssl-context \- key-store, but not on relation authentication-client \- ssl-context ** There is not such feature in other Elytron consumer (Elytron subsystem). * I want to specify provider mainly in case when I want to achieve something special. So when I want to specify ssl-context's provider, there is little chance this provider will serve also for trust-manager. ** For example theoretically I can configure OpenSSL provider for ssl-context, but it won't work for trust-manager was (Author: mchoma): I am not sure if this is good feature or not. As I understand this allows inherit parents element provider - if specified on parent. These are my thoughts: * Consistency ** same feature is on sibling relation ssl-context <\-> key-store, but not on relation authentication-client <\-> ssl-context ** There is not such feature in other Elytron consumer (Elytron subsystem). * I want to specify provider mainly in case when I want to achieve something special. So when I want to specify ssl-context's provider, there is little chance this provider will serve also for trust-manager. ** For example theoretically I can configure OpenSSL provider for ssl-context, but it won't work for trust-manager > 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 > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

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

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1170: ----------------------------------- I am not sure if this is good feature or not. As I understand this allows inherit parents element provider - if specified on parent. These are my thoughts: * Consistency ** same feature is on sibling relation ssl-context <-> key-store, but not on relation authentication-client <-> ssl-context ** There is not such feature in other Elytron consumer (Elytron subsystem). * I want to specify provider mainly in case when I want to achieve something special. So when I want to specify ssl-context's provider, there is little chance this provider will serve also for trust-manager. ** For example theoretically I can configure OpenSSL provider for ssl-context, but it won't work for trust-manager > 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 > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

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

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Martin Choma edited comment on ELY-1170 at 10/18/17 6:57 AM: ------------------------------------------------------------- I am not sure if this is good feature or not. As I understand this allows inherit parents element provider - if specified on parent. These are my thoughts: * Consistency ** same feature is on sibling relation ssl-context <\-> key-store, but not on relation authentication-client <\-> ssl-context ** There is not such feature in other Elytron consumer (Elytron subsystem). * I want to specify provider mainly in case when I want to achieve something special. So when I want to specify ssl-context's provider, there is little chance this provider will serve also for trust-manager. ** For example theoretically I can configure OpenSSL provider for ssl-context, but it won't work for trust-manager was (Author: mchoma): I am not sure if this is good feature or not. As I understand this allows inherit parents element provider - if specified on parent. These are my thoughts: * Consistency ** same feature is on sibling relation ssl-context <-> key-store, but not on relation authentication-client <-> ssl-context ** There is not such feature in other Elytron consumer (Elytron subsystem). * I want to specify provider mainly in case when I want to achieve something special. So when I want to specify ssl-context's provider, there is little chance this provider will serve also for trust-manager. ** For example theoretically I can configure OpenSSL provider for ssl-context, but it won't work for trust-manager > 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 > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1385) Add option to override the TrustManager within <authentication-client ></authentication>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1385?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1385: --------------------------------------- I have already edited the title to reflect that, we actually use our own custom KeyManager impl in there so there is no need to override the algorithm on that one. > Add option to override the TrustManager within <authentication-client ></authentication> > ---------------------------------------------------------------------------------------- > > Key: ELY-1385 > URL: https://issues.jboss.org/browse/ELY-1385 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > > At the moment we can reference an alias from a KeyStore and reference a complete KeyStore for use by the TrustManager but there is not option to override which key and trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1385) Add option to override the TrustManager within <authentication-client ></authentication>

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1385?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1385: ----------------------------------- Looking into PR key-manager part is missing. > Add option to override the TrustManager within <authentication-client ></authentication> > ---------------------------------------------------------------------------------------- > > Key: ELY-1385 > URL: https://issues.jboss.org/browse/ELY-1385 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > > At the moment we can reference an alias from a KeyStore and reference a complete KeyStore for use by the TrustManager but there is not option to override which key and trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1417) Add unseen nonce count tracking support

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1417: ------------------------------------- Summary: Add unseen nonce count tracking support Key: ELY-1417 URL: https://issues.jboss.org/browse/ELY-1417 Project: WildFly Elytron Issue Type: Sub-task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.6.CR1 i.e. the ranges of missing nonce counts we have not yet seen. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1416) Update next nonce issuing to test if current nonce is still usable

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1416: ------------------------------------- Summary: Update next nonce issuing to test if current nonce is still usable Key: ELY-1416 URL: https://issues.jboss.org/browse/ELY-1416 Project: WildFly Elytron Issue Type: Sub-task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.6.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1415) Add last used time tracking to nonces to extend usable window

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1415: ------------------------------------- Summary: Add last used time tracking to nonces to extend usable window Key: ELY-1415 URL: https://issues.jboss.org/browse/ELY-1415 Project: WildFly Elytron Issue Type: Sub-task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.6.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

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

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1414: ------------------------------------- Summary: 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 Assignee: Darran Lofthouse Fix For: 1.1.6.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 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 October 2017