[JBoss JIRA] (WFLY-1136) Common mechanism for all secure socket definitions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-1136?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1136:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Common mechanism for all secure socket definitions
> --------------------------------------------------
>
> Key: WFLY-1136
> URL: https://issues.jboss.org/browse/WFLY-1136
> Project: WildFly
> Issue Type: Sub-task
> 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 was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-1020) Add DeploymentModulePermission
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-1020?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1020:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Add DeploymentModulePermission
> ------------------------------
>
> Key: WFLY-1020
> URL: https://issues.jboss.org/browse/WFLY-1020
> Project: WildFly
> Issue Type: Enhancement
> Components: Server
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 9.0.0.CR1
>
>
> Add a permission which governs the ability of a deployment to load a specific module. The permission should be checked at deploy time for every explicitly added module dependency.
> It may also be wise to automatically add permissions for each implicit module as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-1415) Move away from expensive enum switch
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-1415?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1415:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Move away from expensive enum switch
> ------------------------------------
>
> Key: WFLY-1415
> URL: https://issues.jboss.org/browse/WFLY-1415
> Project: WildFly
> Issue Type: Task
> Reporter: David Lloyd
> Priority: Minor
> Labels: janitor
> Fix For: 9.0.0.CR1
>
>
> We use enums and enum switch extensively. These constructs generate many, many additional classes and bloat the code base unnecessarily.
> All cases where we are using enum-based switches for our XML parsers should be converted to use Java 7 String switch instead. The enum values shall be replaced with String constant fields, all enum switches converted to String switches, and all enum types removed from these classes. The net result should be a reduction by dozens if not hundreds of .class files, and possibly a measurable performance boost as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-1598:
-------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta1)
> Out of the box SSL - or shortly after.
> --------------------------------------
>
> Key: WFLY-1598
> URL: https://issues.jboss.org/browse/WFLY-1598
> Project: WildFly
> Issue Type: Sub-task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: management_security,, management_sso
> Fix For: 9.0.0.CR1
>
>
> There are various reasons that we do not support SSL/TLS out of the box e.g.
> - If we ship a default keystore then everyone has access to the private key.
> - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead.
> This issue is to explorer other options to encourage their use and make it easier to configure.
> As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month