[
https://issues.redhat.com/browse/WFCORE-5095?page=com.atlassian.jira.plug...
]
Farah Juma moved EAP7-1546 to WFCORE-5095:
------------------------------------------
Project: WildFly Core (was: JBoss EAP Planning for version 7
and above)
Key: WFCORE-5095 (was: EAP7-1546)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow
2.0)
Component/s: Security
(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)
Add the ability to make use of an automatically generated self-signed
certificate with Elytron
----------------------------------------------------------------------------------------------
Key: WFCORE-5095
URL:
https://issues.redhat.com/browse/WFCORE-5095
Project: WildFly Core
Issue Type: Feature Request
Components: Security
Reporter: Farah Juma
Assignee: Farah Juma
Priority: Major
Labels: Active-Development
EAP7-584 added the ability to lazily generate a self-signed certificate on first use for
a specified host name when using legacy security. This RFE is to provide similar
functionality when Elytron is in use. Like with legacy security, it will be important to
log a warning message so the user knows that a self-signed certificate is being used and
to indicate that this certificate should not be used in a production environment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)