2:43 p.m.
Common mechanism for all secure socket definitions
--------------------------------------------------
Key: JBAS-8134
URL: https://jira.jboss.org/browse/JBAS-8134
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: Unscheduled
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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-8134) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/JBAS-8134?page=com.atlassian.jira.plugin....
]
Jason Greene reopened JBAS-8134:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all
unscheduled AS6 issues that are a year or less old. This will make it easier community
members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate
them.
Common mechanism for all secure socket definitions
--------------------------------------------------
Key: JBAS-8134
URL: https://issues.jboss.org/browse/JBAS-8134
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Fix For: No Release
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:20 a.m.
New subject: [JBoss JIRA] Updated: (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-639:
-----------------------------
Fix Version/s: 7.1.0.Alpha1
(was: 7.0.0.CR1)
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
Reporter: Brian Stansberry
Fix For: 7.1.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:31 p.m.
New subject: [JBoss JIRA] Updated: (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-639:
---------------------------------
Component/s: Domain Management
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
Reporter: Brian Stansberry
Fix For: 7.1.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 p.m.
New subject: [JBoss JIRA] Updated: (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-639:
-----------------------------
Fix Version/s: 7.1.0.Beta1
(was: 7.1.0.Alpha1)
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
Reporter: Brian Stansberry
Fix For: 7.1.0.Beta1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:48 p.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-639:
---------------------------------
Component/s: Security
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
Fix For: 7.1.0.Beta1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:26 p.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
David Lloyd updated AS7-639:
----------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Beta1)
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
Fix For: 7.1.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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 p.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-639:
---------------------------------
Fix Version/s: 7.2.0.Alpha1
(was: 7.1.0.Final)
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
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:52 a.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Darran Lofthouse updated AS7-639:
---------------------------------
Assignee: Darran Lofthouse
Taking owbership as unifying the authenticators with the realms is something I am planning
to review further for AS 7.2.x
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: Darran Lofthouse
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 a.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry commented on AS7-639:
--------------------------------------
Darran, ping Tomaz Cerar about this, as he's doing some refactoring now in web and
mod-cluster subsystems, both of which are big SSL config use cases.
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: Darran Lofthouse
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:34 a.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Tomaz Cerar reassigned AS7-639:
-------------------------------
Assignee: Tomaz Cerar (was: Darran Lofthouse)
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
9:48 a.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
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
9:48 a.m.
New subject: [JBoss JIRA] (AS7-639) Common mechanism for all secure socket definitions
[
https://issues.jboss.org/browse/AS7-639?page=com.atlassian.jira.plugin.sy...
]
Tomaz Cerar updated AS7-639:
----------------------------
Comment: was deleted
(was: Due to feedback from the community, I have split the AS7 and AS6 projects and
reopened all unscheduled AS6 issues that are a year or less old. This will make it easier
community members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate
them.)
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
4464
days inactive
5297
days old
12 comments
6 participants
participants (6)
-
Brian Stansberry (JIRA) -
Brian Stansberry (Updated) (JIRA)
-
Darran Lofthouse (JIRA)
-
David Lloyd (Updated) (JIRA)
-
Jason Greene (JIRA)
-
Tomaz Cerar (JIRA)