[jboss-jira] [JBoss JIRA] (WFLY-1136) Common mechanism for all secure socket definitions
Darran Lofthouse (JIRA)
issues at jboss.org
Thu Nov 10 07:07:00 EST 2016
[ https://issues.jboss.org/browse/WFLY-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darran Lofthouse resolved WFLY-1136.
------------------------------------
Resolution: Done
Resolving as the Elytron integration now provided capabilities for various SSL types - individual subsystems will continue to be migrated independently to use these.
> Common mechanism for all secure socket definitions
> --------------------------------------------------
>
> Key: WFLY-1136
> URL: https://issues.jboss.org/browse/WFLY-1136
> Project: WildFly
> Issue Type: Sub-task
> Components: Domain Management, Security
> Reporter: Brian Stansberry
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
> >> The JAASSecurityDomain in my opinion should
> >> handle all secure socket definitions. Mod-cluster currently does
> >> not support JAASSecurityDomains.
> I won't comment either way on whether JAASSecurityDomain is how we'll do this, but I definitely agree that a common mechanism should be used for all secure socket definitions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list