[JBoss JIRA] (WFLY-379) Fix & re-enable ignored security tests
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-379?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-379:
------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Fix & re-enable ignored security tests
> --------------------------------------
>
> Key: WFLY-379
> URL: https://issues.jboss.org/browse/WFLY-379
> Project: WildFly
> Issue Type: Sub-task
> Components: Security
> Affects Versions: 8.0.0.Alpha1
> Environment: AS8 with undertow
> Reporter: Tomaz Cerar
> Assignee: Darran Lofthouse
> Fix For: 10.0.0.Alpha3
>
>
> AS8 with undertow fails few security tests.
> This issue is here just for tracking what they are so they can be fixed
> Still disabled tests:
> {noformat}
> SPNEGOLoginModuleTestCase
> AdvancedLdapLoginModuleTestCase
> StackingJASPITestCase
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-442) Review of AccessController and PrivilegedAction use across AS7
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-442?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-442:
------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Review of AccessController and PrivilegedAction use across AS7
> --------------------------------------------------------------
>
> Key: WFLY-442
> URL: https://issues.jboss.org/browse/WFLY-442
> Project: WildFly
> Issue Type: Task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: investigation_required
> Fix For: 10.0.0.Alpha3
>
>
> The following needs reviewing across AS7: -
> - On demand instantiation of PrivilegedActions where singletons would suffice (Consider frequency of calls, gc may be preferable).
> - Use of AccessController even though there is no SecurityManager set.
> - Code duplication, in every case I have seen so far the code is the same regardless of if PRIVILEGED or NON_PRIVILEGED
> - Utility methods with visibility too high.
> - In depth review of the other methods, i.e. if the first thing a public method does is set the class loader based on a parameter passed in it could be used badly - it may even be a justification for that method to NOT use a PrivilegedAction.
> - Code that requires to be executed using a PrivilegedAction should also be double checked that it is not doing too much as the identity of the caller.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-431) Revisit enforcement of required file system permissions.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-431?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-431:
------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Revisit enforcement of required file system permissions.
> --------------------------------------------------------
>
> Key: WFLY-431
> URL: https://issues.jboss.org/browse/WFLY-431
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: management_security,
> Fix For: 10.0.0.Alpha3
>
>
> Now that AS8 has moved to Java 7 we can re-visit the level of control we have over file system permissions, this can be from taking more control of the local authentication mechanism to ensure incorrect permissions are not inherited to verifying sensitive configuration files are not world readable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-421) Domain Mode JMX access through the HostController
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-421?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-421:
------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Domain Mode JMX access through the HostController
> -------------------------------------------------
>
> Key: WFLY-421
> URL: https://issues.jboss.org/browse/WFLY-421
> Project: WildFly
> Issue Type: Task
> Components: JMX, Remoting
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: JMX, investigation_required
> Fix For: 10.0.0.Alpha3
>
>
> This task is first to review if this should be considered.
> At the moment access to JMX is provided through the remoting connector of each AS instance - this task is to consider if we should actually make it available through the host controller with the host controller acting as a proxy.
> The main motivation being to separate management and app traffic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-466) Detect JBossWS Configuration for @PermitAll endpoints within Undertow subsystem.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-466?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-466:
------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Detect JBossWS Configuration for @PermitAll endpoints within Undertow subsystem.
> --------------------------------------------------------------------------------
>
> Key: WFLY-466
> URL: https://issues.jboss.org/browse/WFLY-466
> Project: WildFly
> Issue Type: Task
> Components: Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 10.0.0.Alpha3
>
>
> UNDERTOW-38 has added the possibility of deploying web applications where authentication is mandated but no authorization checks are performed - this is required for integration use cases such as EJB endpoints where authorization checks are being left to the EJB container.
> This task is to update the Undertow susbsystem to detect this scenario and enable the new mode for UNDERTOW-38.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months
[JBoss JIRA] (WFLY-447) Connection Reauthentication and Security Propagation
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-447?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-447:
------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Connection Reauthentication and Security Propagation
> ----------------------------------------------------
>
> Key: WFLY-447
> URL: https://issues.jboss.org/browse/WFLY-447
> Project: WildFly
> Issue Type: Task
> Components: EJB, Remoting, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: authentication_service
> Fix For: 10.0.0.Alpha3
>
>
> This task is a top level task to coordinate the addition of support for switching to different security identities on an existing connection over Remoting.
> This is to predominantly cover two major scenarios: -
> - Clients using a single connection but require different calls to be executed as different users, in this case the client has the information required to start a new authentication as a different user.
> - Server to server communication where the first server has already authenticated a remote user - for this scenario the first server needs a way to tell the second server what identity to run the call as.
> The following document is building up the requirements and design considerations and decisions: -
> https://community.jboss.org/wiki/ConnectionRe-AuthenticationAndSecurityPr...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 7 months