Page History
Securing the cookie
In this section we will explain how to secure the cookie depending on the Blueriq Runtime you are using. (Java or .NET version)
Java Runtime
In the Java Runtime the way of securing the cookie differs between R10 and R9 or older versions.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
server.session.cookie.secure=true # "Secure" flag for the session cookie. |
.NET Runtime
In the .NET Runtime there is no difference in in the way of securing the cookie between R10 and R9 or older versions.
...
| Note |
|---|
The Blueriq cookie is not secured by default. Securing the cookie should take place on the same location where the SSL offloading is done. The reason behind this, is because it is not possible to send a cookie with the secure flag set over an unencrypted HTTP request. For example, if the SSL offloading is done by the loadbalancer, here the secure flag should be enabled and disabled. The only use case to enable the secure flag as specified above is when offloading takes place on the application server where the Runtime is deployed (Tomcat, JBoss, Websphere). |
Timeout
In this section we will explain how to set the session timeout depending on the Blueriq Runtime you are using. (Java or .NET version)
Java Runtime
In the Java Runtime the way of defining the session timeout differs between R10 and R9 or older versions.
...
| Info |
|---|
If you are upgrading from R9 to R10 pay attention to the session timeout measurement unit. If in R9 or older versions, the value is specified in minutes, in R10 the value is specified in seconds. |
.NET Runtime
In the .NET Runtime there is no difference in in the way of specifying the session timeout between R10 and R9 or older versions.
...
Overview
Content Tools