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

[Darran Lofthouse (JIRA)]

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

Darran Lofthouse commented on WFLY-1136:
----------------------------------------

We are at the point where we have many services that require access to a pre-instantiated SSLConext, it is the configuration of this context and the key and trust managers used to initialise it that we really need to get shifted into the common config.

Additionally this needs to be further considered in the context of re-using schemas and code within subsystems and within pure management processes without subsystems.  With code re-use we also can consider do we define this within one susbysytem and let the others reference it or with re-use do we allow each subsystem to define that 'A SSLContext can be defined here' and re-use the code, XML handling, schemas, resource definitions, service handling etc...

                
> 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