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