[Red Hat JIRA] (ELY-2058) Accepted Issuers should not be manually configured in X509RevocationTrustManager
by Sonia Zaldana (Jira)
[ https://issues.redhat.com/browse/ELY-2058?page=com.atlassian.jira.plugin.... ]
Sonia Zaldana updated ELY-2058:
-------------------------------
Description:
In the X509RevocationTrustManager.Builder class, we can currently configure the trust manager's accepted issuers. However, the accepted issuers should only be the certificates stored in the trust store.
Allowing users to specify their own accepted issuers could contradict the trust store's actual accepted issuers.
> Accepted Issuers should not be manually configured in X509RevocationTrustManager
> --------------------------------------------------------------------------------
>
> Key: ELY-2058
> URL: https://issues.redhat.com/browse/ELY-2058
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Sonia Zaldana
> Assignee: Sonia Zaldana
> Priority: Major
>
> In the X509RevocationTrustManager.Builder class, we can currently configure the trust manager's accepted issuers. However, the accepted issuers should only be the certificates stored in the trust store.
> Allowing users to specify their own accepted issuers could contradict the trust store's actual accepted issuers.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFCORE-5033) Move org.wildfly.security:wildfly-elytron-jacc into it's own module
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFCORE-5033?page=com.atlassian.jira.plug... ]
Jeff Mesnil updated WFCORE-5033:
--------------------------------
Fix Version/s: 14.0.0.Beta5
(was: 14.0.0.Beta4)
> Move org.wildfly.security:wildfly-elytron-jacc into it's own module
> -------------------------------------------------------------------
>
> Key: WFCORE-5033
> URL: https://issues.redhat.com/browse/WFCORE-5033
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 14.0.0.Beta5
>
>
> Long term it will be desirable for JACC to be within it's own subsystem so it's inclusion can be controlled using layers, however there may be an intermediate step where we split JACC out from the Elytron project so will want to bring it in ideally in it's own module.
> The classes within this module have never been public API so we are free to refactor as needed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months