[
https://issues.redhat.com/browse/ELY-1996?page=com.atlassian.jira.plugin....
]
Farah Juma moved EAP7-1502 to ELY-1996:
---------------------------------------
Project: WildFly Elytron (was: JBoss EAP Planning for version 7
and above)
Key: ELY-1996 (was: EAP7-1502)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow
2.0)
Component/s: (was: Security)
EAP PT Pre-Checked (PC): (was: TODO)
Target Release: (was: 7.4.0.GA)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Product Docs (PD): (was: New)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
EAP PT Analysis Document (AD): (was: TODO)
SSLContext to support delegation to alternate instances based on peer
information.
----------------------------------------------------------------------------------
Key: ELY-1996
URL:
https://issues.redhat.com/browse/ELY-1996
Project: WildFly Elytron
Issue Type: Feature Request
Reporter: Farah Juma
Assignee: Diana Vilkolakova
Priority: Major
Labels: Active-Development
As an SSLEngine is created the host and port information is available at the time the
engine is requested: -
https://download.java.net/java/early_access/jdk11/docs/api/java.base/java...
We could make use of this information to dynamically select alternative configurations.
This would also be a natural follow up to EAP7-1096 so the registered SSLContext could
delegate to different configurations based on destination.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)