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

Tomaz Cerar (JIRA) jira-events at lists.jboss.org
Tue Oct 9 10:48:04 EDT 2012


     [ https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar updated AS7-639:
----------------------------

    Comment: was deleted

(was: Now that work is underway with AS7 all previous community releases are end-of-lifed. So, all issues not directly assigned to an AS7 release are being closed.

JBoss EAP is our supported enterprise version of AS, and you can file your issues against any release during its very long support window via  CSP/RHN.

If you believe your issue is still relevant to AS7 then please verify it and reopen.)

    
> Common mechanism for all secure socket definitions
> --------------------------------------------------
>
>                 Key: AS7-639
>                 URL: https://issues.jboss.org/browse/AS7-639
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management, Security
>            Reporter: Brian Stansberry
>            Assignee: Tomaz Cerar
>             Fix For: 7.2.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 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