[
https://issues.jboss.org/browse/WFLY-7260?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on WFLY-7260:
----------------------------------------
[~honza889] How relevant is this now? If both are set to true then 'need' will
always have the highest priority - if one is set to false your latest code within Elytron
handles that correctly now.
Document in elytron model *-client-auth are mutual exclusive
------------------------------------------------------------
Key: WFLY-7260
URL:
https://issues.jboss.org/browse/WFLY-7260
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Assignee: Jan Kalina
Priority: Minor
Add to documentation information that need-client-auth and want-client-auth are mutually
exclusive. If one is set other is unset.
Now we just have:
* {{want-client-auth}} - "Set wantClientAuth on the underlying SSLContext - if a
security domain is referenced this will automatically be set to true."
* {{need-client-auth}} - "Set needClientAuth on the underlying SSLContext."
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)