[JBoss JIRA] (WFLY-6543) Multiple Sessions are created over SSL Session Tracking
by Pradeep Kumar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6543?page=com.atlassian.jira.plugin.... ]
Pradeep Kumar updated WFLY-6543:
--------------------------------
Description:
When using SSL as the session tracking method, there are multiple sessions created for subsequent HTTP requests, some of which are reused.
This is the log obtained by using a filter to track the HTTP Sessions:
{noformat}
14:08:45,766 INFO [com.test.SessionIdTrackFilter] (default task-17) Request URL : [/SessionTrackingSsl/], Session Id : [wkgBkT61gFQnJeSacPyLEgKWmJ6iPusT-8xcpXFP]
14:08:45,784 INFO [com.test.SessionIdTrackFilter] (default task-20) Request URL : [/SessionTrackingSsl/resources/css/font-awesome.min.css], Session Id : [uljMhXUsAK1BXXXmnmXzAD4EkFgFZn30I-wsFajD]
14:08:45,784 INFO [com.test.SessionIdTrackFilter] (default task-16) Request URL : [/SessionTrackingSsl/resources/js/jquery/jquery-1.12.3.min.js], Session Id : [SBZeTDPKSxLbgcwR_zCazx5heXwssOvrjSVI0sJV]
14:08:45,784 INFO [com.test.SessionIdTrackFilter] (default task-18) Request URL : [/SessionTrackingSsl/resources/css/bootstrap.min.css], Session Id : [wkgBkT61gFQnJeSacPyLEgKWmJ6iPusT-8xcpXFP]
14:08:45,785 INFO [com.test.SessionIdTrackFilter] (default task-16) Request URL : [/SessionTrackingSsl/resources/js/bootstrap.min.js], Session Id : [FETLRFRjQyjzktTUi29hTe3tqimJnGEgdpHZGu6e]
14:08:45,787 INFO [com.test.SessionIdTrackFilter] (default task-19) Request URL : [/SessionTrackingSsl/starter-template.css], Session Id : [eHGhpdreJJv8RKTmZul3hKXjORhAp8GIqJktTmgh]
14:08:45,814 INFO [com.test.SessionIdTrackFilter] (default task-26) Request URL : [/SessionTrackingSsl/resources/fonts/fontawesome-webfont.woff2], Session Id : [wkgBkT61gFQnJeSacPyLEgKWmJ6iPusT-8xcpXFP]
{noformat}
I have made the following changes to the standalone.xml to enable SSL:
diff ../standalone/configuration/standalone.xml ../standalone/configuration/standalone_xml_history/standalone.initial.xml :
{noformat}
1c1
< <?xml version='1.0' encoding='UTF-8'?>
---
> <?xml version="1.0" ?>
4d3
<
33,34d31
<
<
47,51d43
< <server-identities>
< <ssl>
< <keystore path="testks.keystore" relative-to="jboss.server.config.dir" keystore-password="Password" alias="testks" key-password="Password"/>
< </ssl>
< </server-identities>
89d80
<
188a180
> <!-- Automatically configure pools. Alternatively, max-pool-size can be set to a specific value -->
206c198
< <remote connector-ref="https-remoting-connector" thread-pool-name="default"/>
---
> <remote connector-ref="http-remoting-connector" thread-pool-name="default"/>
305c297
< <http-connector name="https-remoting-connector" connector-ref="default-https" security-realm="ApplicationRealm"/>
---
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
360c352
< <https-listener name="default-https" security-realm="ApplicationRealm" socket-binding="https"/>
---
> <http-listener name="default" socket-binding="http" redirect-socket="https"/>
391d382
<
400d390
<
{noformat}
Apart from this, I have not made any changes to any of the configuration files. When the tracking method is set to COOKIE, the session ids are consistent.
was:
When using SSL as the session tracking method, there are multiple sessions created for subsequent HTTP requests, some of which are reused.
Steps to Reproduce:
1. Enable SSL.
2. Deploy the attachment "SessionTrackingSsl.war".
3. Access the resource through the browser.
4. The Session Ids will be logged to the configured root logger.
Sometimes the session ids are consistent. In such cases, clearing the browser data and reloading the resource will help reproduce the bug. But
Attachment: SessionTrackingSsl.war
Labels: session ssl (was: )
Environment: oracle java version "1.8.0_74"
> Multiple Sessions are created over SSL Session Tracking
> -------------------------------------------------------
>
> Key: WFLY-6543
> URL: https://issues.jboss.org/browse/WFLY-6543
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Final
> Environment: oracle java version "1.8.0_74"
> Reporter: Pradeep Kumar
> Assignee: Stuart Douglas
> Labels: session, ssl
> Attachments: SessionTrackingSsl.war
>
>
> When using SSL as the session tracking method, there are multiple sessions created for subsequent HTTP requests, some of which are reused.
> This is the log obtained by using a filter to track the HTTP Sessions:
> {noformat}
> 14:08:45,766 INFO [com.test.SessionIdTrackFilter] (default task-17) Request URL : [/SessionTrackingSsl/], Session Id : [wkgBkT61gFQnJeSacPyLEgKWmJ6iPusT-8xcpXFP]
> 14:08:45,784 INFO [com.test.SessionIdTrackFilter] (default task-20) Request URL : [/SessionTrackingSsl/resources/css/font-awesome.min.css], Session Id : [uljMhXUsAK1BXXXmnmXzAD4EkFgFZn30I-wsFajD]
> 14:08:45,784 INFO [com.test.SessionIdTrackFilter] (default task-16) Request URL : [/SessionTrackingSsl/resources/js/jquery/jquery-1.12.3.min.js], Session Id : [SBZeTDPKSxLbgcwR_zCazx5heXwssOvrjSVI0sJV]
> 14:08:45,784 INFO [com.test.SessionIdTrackFilter] (default task-18) Request URL : [/SessionTrackingSsl/resources/css/bootstrap.min.css], Session Id : [wkgBkT61gFQnJeSacPyLEgKWmJ6iPusT-8xcpXFP]
> 14:08:45,785 INFO [com.test.SessionIdTrackFilter] (default task-16) Request URL : [/SessionTrackingSsl/resources/js/bootstrap.min.js], Session Id : [FETLRFRjQyjzktTUi29hTe3tqimJnGEgdpHZGu6e]
> 14:08:45,787 INFO [com.test.SessionIdTrackFilter] (default task-19) Request URL : [/SessionTrackingSsl/starter-template.css], Session Id : [eHGhpdreJJv8RKTmZul3hKXjORhAp8GIqJktTmgh]
> 14:08:45,814 INFO [com.test.SessionIdTrackFilter] (default task-26) Request URL : [/SessionTrackingSsl/resources/fonts/fontawesome-webfont.woff2], Session Id : [wkgBkT61gFQnJeSacPyLEgKWmJ6iPusT-8xcpXFP]
> {noformat}
> I have made the following changes to the standalone.xml to enable SSL:
> diff ../standalone/configuration/standalone.xml ../standalone/configuration/standalone_xml_history/standalone.initial.xml :
> {noformat}
> 1c1
> < <?xml version='1.0' encoding='UTF-8'?>
> ---
> > <?xml version="1.0" ?>
> 4d3
> <
> 33,34d31
> <
> <
> 47,51d43
> < <server-identities>
> < <ssl>
> < <keystore path="testks.keystore" relative-to="jboss.server.config.dir" keystore-password="Password" alias="testks" key-password="Password"/>
> < </ssl>
> < </server-identities>
> 89d80
> <
> 188a180
> > <!-- Automatically configure pools. Alternatively, max-pool-size can be set to a specific value -->
> 206c198
> < <remote connector-ref="https-remoting-connector" thread-pool-name="default"/>
> ---
> > <remote connector-ref="http-remoting-connector" thread-pool-name="default"/>
> 305c297
> < <http-connector name="https-remoting-connector" connector-ref="default-https" security-realm="ApplicationRealm"/>
> ---
> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
> 360c352
> < <https-listener name="default-https" security-realm="ApplicationRealm" socket-binding="https"/>
> ---
> > <http-listener name="default" socket-binding="http" redirect-socket="https"/>
> 391d382
> <
> 400d390
> <
> {noformat}
> Apart from this, I have not made any changes to any of the configuration files. When the tracking method is set to COOKIE, the session ids are consistent.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ELY-507) Add ability to forward requests.
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-507:
------------------------------------
Summary: Add ability to forward requests.
Key: ELY-507
URL: https://issues.jboss.org/browse/ELY-507
Project: WildFly Elytron
Issue Type: Enhancement
Components: API / SPI, HTTP
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.1.0.Beta6
Authentication mechanisms that rely on sending a whole page to the client may want this handled inside the server instead of sending a redirect - this enables mechanisms such as FORM authentication to be compatible with other mechanisms such as SPNEGO and also eliminates an additional round trip just to display a form.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6543) Multiple Sessions are created over SSL Session Tracking
by Pradeep Kumar (JIRA)
Pradeep Kumar created WFLY-6543:
-----------------------------------
Summary: Multiple Sessions are created over SSL Session Tracking
Key: WFLY-6543
URL: https://issues.jboss.org/browse/WFLY-6543
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.0.0.Final
Reporter: Pradeep Kumar
Assignee: Stuart Douglas
When using SSL as the session tracking method, there are multiple sessions created for subsequent HTTP requests, some of which are reused.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ELY-506) Strongly typed getAttachment method on HttpScope
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-506:
------------------------------------
Summary: Strongly typed getAttachment method on HttpScope
Key: ELY-506
URL: https://issues.jboss.org/browse/ELY-506
Project: WildFly Elytron
Issue Type: Feature Request
Components: API / SPI, HTTP
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.1.0.Beta6
This is more a utility method on the interface, can type a type and if the item is stored in the scope and has that type it can be automatically cast.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6539) SingletonDeploymentDescriptorTestCase and SingletonDeploymentJBossAllTestCase fails due to http-trace disallowed
by Ivan Straka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6539?page=com.atlassian.jira.plugin.... ]
Ivan Straka edited comment on WFLY-6539 at 4/21/16 4:33 AM:
------------------------------------------------------------
Actually no. Tests fail in CR2 for TCP ASYNC and UDB SYNC/ASYNC configurations. Http-trace is allowed only for TCP SYNC configuration.
See https://github.com/wildfly/wildfly/blob/master/testsuite/integration/src/...
ant target for enabling http-trace is called only for tcp sync configuration. Not for extended tests.
I should have provide these informations in description. I am sorry.
was (Author: istraka):
Actually no. Tests fail in CR2 for TCP ASYNC and UDB SYNC/ASYNC configurations. Http-trace is allowed only for TCP SYNC configuration.
See https://github.com/wildfly/wildfly/blob/master/testsuite/integration/src/...
ant target for enabling http-trace is called only for tcp sync configuration. Not for extended tests.
> SingletonDeploymentDescriptorTestCase and SingletonDeploymentJBossAllTestCase fails due to http-trace disallowed
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6539
> URL: https://issues.jboss.org/browse/WFLY-6539
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.Final
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Minor
>
> There are two tests
> * SingletonDeploymentDescriptorTestCase
> * SingletonDeploymentJBossAllTestCase
> that fails because http-trace is disallowed
> {code:java}
> Error Details
> expected:<200> but was:<405>
> Stack Trace
> java.lang.AssertionError: expected:<200> but was:<405>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at org.jboss.as.test.clustering.cluster.singleton.SingletonDeploymentTestCase.test(SingletonDeploymentTestCase.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ...
> {code}
> We need to enable http-trace requests in clustering configurations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6539) SingletonDeploymentDescriptorTestCase and SingletonDeploymentJBossAllTestCase fails due to http-trace disallowed
by Ivan Straka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6539?page=com.atlassian.jira.plugin.... ]
Ivan Straka reopened WFLY-6539:
-------------------------------
Actually no. Tests fail in CR2 for TCP ASYNC and UDB SYNC/ASYNC configurations. Http-trace is allowed only for TCP SYNC configuration.
See https://github.com/wildfly/wildfly/blob/master/testsuite/integration/src/...
ant target for enabling http-trace is called only for tcp sync configuration. Not for extended tests.
> SingletonDeploymentDescriptorTestCase and SingletonDeploymentJBossAllTestCase fails due to http-trace disallowed
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6539
> URL: https://issues.jboss.org/browse/WFLY-6539
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.Final
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Minor
>
> There are two tests
> * SingletonDeploymentDescriptorTestCase
> * SingletonDeploymentJBossAllTestCase
> that fails because http-trace is disallowed
> {code:java}
> Error Details
> expected:<200> but was:<405>
> Stack Trace
> java.lang.AssertionError: expected:<200> but was:<405>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at org.jboss.as.test.clustering.cluster.singleton.SingletonDeploymentTestCase.test(SingletonDeploymentTestCase.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ...
> {code}
> We need to enable http-trace requests in clustering configurations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (DROOLS-1134) Business central items are not visible in Kie navigator when other than default git path is used
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1134?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky closed DROOLS-1134.
-------------------------------------
[~tomasdavidorg] wrote "Verified with JBDS 9.1.0.Beta2 and Drools plugin 6.4.0.201601201107."
> Business central items are not visible in Kie navigator when other than default git path is used
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1134
> URL: https://issues.jboss.org/browse/DROOLS-1134
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Labels: release_notes, verified_jbdsis-9.0.0
> Fix For: 6.4.0.Final
>
>
> Description of problem:
> When Git Repository Path is set to another location than default (not the checkbox but the default filled path), business central items (rules, pom.xml and other files) are not visible in kie navigator.
> Version-Release number of selected component (if applicable):
> Drools 6.3.0.Final
> How reproducible:
> -
> Steps to Reproduce:
> 1. Set up and run a server.
> 2. Open Kie navigator, open properties for the server and change Git repository path.
> 3. Open org unit, open repository, error "Invalid remote origin" is displayed, see the attachment.
> 4. Open project. Browse project.
> Actual results:
> No items are visible.
> Expected results:
> Items (rules, pom.xml, ...) are visible.
> For more info see https://bugzilla.redhat.com/show_bug.cgi?id=1269100
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (DROOLS-1134) Business central items are not visible in Kie navigator when other than default git path is used
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1134?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky resolved DROOLS-1134.
---------------------------------------
Fix Version/s: 6.4.0.Final
Resolution: Done
> Business central items are not visible in Kie navigator when other than default git path is used
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1134
> URL: https://issues.jboss.org/browse/DROOLS-1134
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Fix For: 6.4.0.Final
>
>
> Description of problem:
> When Git Repository Path is set to another location than default (not the checkbox but the default filled path), business central items (rules, pom.xml and other files) are not visible in kie navigator.
> Version-Release number of selected component (if applicable):
> Drools 6.3.0.Final
> How reproducible:
> -
> Steps to Reproduce:
> 1. Set up and run a server.
> 2. Open Kie navigator, open properties for the server and change Git repository path.
> 3. Open org unit, open repository, error "Invalid remote origin" is displayed, see the attachment.
> 4. Open project. Browse project.
> Actual results:
> No items are visible.
> Expected results:
> Items (rules, pom.xml, ...) are visible.
> For more info see https://bugzilla.redhat.com/show_bug.cgi?id=1269100
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years