[
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)