[jboss-jira] [JBoss JIRA] (WFLY-1136) Common mechanism for all secure socket definitions

[Tomaz Cerar (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12945558#comment-12945558 ] 

Tomaz Cerar commented on WFLY-1136:
-----------------------------------

This mostly the same as we did with for xnio configuration in IO subsystem as part of WFLY-2055
IO subsystem had common configuration there + bunch of APIs that other subsystems(remoting, undertow, ..) that would need to configure XNIO options could use.

                
> 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