Versions Compared

Old Version 2

changes.mady.by.user Voicu Moldovan

Saved on

compared with

New Version 3

changes.mady.by.user Unknown User (s.wartenberg)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Securing the cookie

In this section we will present how to secure the cookie depending on the which 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.

For R9 or older versions, the value (true | false) is specified in the deployment descriptor (web.xml):

Code Block
languagexml
linenumberstrue
<web-app ...>
	<session-config>
		<secure>true</secure>
	</session-config>
</web-app>

For R10 we benefit of various spring boot common properties that can be specified inside bootstrap.properties or it can be given as a VM argument.

Code Block
languagexml
linenumberstrue
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. 

The value is specified in Web.config under <system.web> tag:

Code Block
languagexml
linenumberstrue
<system.web>
 <httpCookies requireSSL="true" />
</system.web>
Note

The Blueriq 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 present how to set the session timeout depending on the which 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. 

...