[JBoss JIRA] (WFLY-466) Detect JBossWS Configuration for @PermitAll endpoints within Undertow subsystem.
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-466?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar reassigned WFLY-466:
--------------------------------
Assignee: Darran Lofthouse (was: Jeff Mesnil)
> 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 (JBoss Web)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.Alpha1
>
>
> 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 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
11 years, 8 months
[JBoss JIRA] (WFLY-423) Allow management of all current Remoting connections (inbound and outbound)
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-423?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated WFLY-423:
----------------------------------
Assignee: Darran Lofthouse (was: Brian Stansberry)
> Allow management of all current Remoting connections (inbound and outbound)
> ---------------------------------------------------------------------------
>
> Key: WFLY-423
> URL: https://issues.jboss.org/browse/WFLY-423
> Project: WildFly
> Issue Type: Task
> Components: Remoting
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: Remoting_Management
> Fix For: 8.0.0.Alpha1
>
>
> This task is to make it possible to view the details of all currently established Remoting connections and to allow termination of these connections.
> In addition to seeing the open connections it should be possible to see the channels opened by each connection. Also while starting on a connection first view you may also want to start on a channel first view i.e. all JNDI users or all EJB users.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-110) WebSSLDefinition NAME attribute is read-write
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-110?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar reassigned WFLY-110:
--------------------------------
Assignee: Tomaz Cerar (was: Brian Stansberry)
> WebSSLDefinition NAME attribute is read-write
> ---------------------------------------------
>
> Key: WFLY-110
> URL: https://issues.jboss.org/browse/WFLY-110
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Web (JBoss Web)
> Reporter: Brian Stansberry
> Assignee: Tomaz Cerar
> Priority: Minor
> Fix For: 8.0.0.CR1
>
>
> WebSSLDefinition has a read-write attribute NAME that AFAICT merely stores the name of an xml element. If the attribute represents part of a resource address it should be read-only. If it's just some cruft (which appears to be the case), it should be deprecated and removed in some later release.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-110) WebSSLDefinition NAME attribute is read-write
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-110?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar updated WFLY-110:
-----------------------------
Component/s: Web (Undertow)
(was: Web (JBoss Web))
> WebSSLDefinition NAME attribute is read-write
> ---------------------------------------------
>
> Key: WFLY-110
> URL: https://issues.jboss.org/browse/WFLY-110
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Web (Undertow)
> Reporter: Brian Stansberry
> Assignee: Tomaz Cerar
> Priority: Minor
> Fix For: 8.0.0.CR1
>
>
> WebSSLDefinition has a read-write attribute NAME that AFAICT merely stores the name of an xml element. If the attribute represents part of a resource address it should be read-only. If it's just some cruft (which appears to be the case), it should be deprecated and removed in some later release.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-406) Redesign web session clustering
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-406?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated WFLY-406:
----------------------------------
Assignee: Paul Ferraro (was: Brian Stansberry)
> Redesign web session clustering
> -------------------------------
>
> Key: WFLY-406
> URL: https://issues.jboss.org/browse/WFLY-406
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Alpha1
>
>
> The current web session replication code has been around for ages and suffers from a number of issues:
> * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - an number of issues have cropped up in EAP testing.
> * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache.
> * Extra logic/locking is required to invalidate the local session map is required per request
> * AtomicMaps, on which the currently implementation relies, have proven buggy
> * Session access outside of the scope of the replication valve is possible and problematic
> * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities.
> * The current code base is tightly coupled to JBoss Web. Migrating the code to support Undertow will inevitably introduce issues and code duplication.
> The new design will incorporate a proper SPI for the servlet container. Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin.
--
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
11 years, 8 months