[jboss-jira] [JBoss JIRA] (WFLY-1136) Common mechanism for all secure socket definitions
Darran Lofthouse (JIRA)
issues at jboss.org
Tue Feb 18 09:53:48 EST 2014
[ https://issues.jboss.org/browse/WFLY-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12945578#comment-12945578 ]
Darran Lofthouse commented on WFLY-1136:
----------------------------------------
One additional clarification, from the original title and description it could be assumed we are talking about inbound server sockets but this configuration also needs to apply to outbound connections as well.
> Common mechanism for all secure socket definitions
> --------------------------------------------------
>
> Key: WFLY-1136
> URL: https://issues.jboss.org/browse/WFLY-1136
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management, Security
> Reporter: Brian Stansberry
> Assignee: Darran Lofthouse
> Fix For: 9.0.0.CR1
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list