Cookie Management

Web Browsers have updated their policy regarding Cookies, and these changes must be applied to your Web Client if you want to embed Nectari into your ERP website, change your Web Client binding from HTTP to HTTPS or use Single Sign-On (SSO) authentication.

 

In order to apply these changes, you will have to edit the web.config file located in C:\inetpub\wwwroot\WebClient.

Attributes to be changed in Nectari web.config file Value before change Value after change
cookieSameSite 
<sessionState cookieSameSite="Lax"/>
 
<sessionState cookieSameSite="None"/>
httpOnlyCookies / requireSSL / sameSite 
<httpCookies httpOnlyCookies="true" requireSSL="false" sameSite="Lax"/>
 
<httpCookies httpOnlyCookies="true" requireSSL="true" sameSite="None"/>

 

Embedding Nectari

Please reference the following IFrame examples for HTTP and HTTPS when embedding Nectari into your ERP website:

HTTP

  • HTTP host embedding HTTP Nectari

  • Same domain name

  • SameSite cookie attribute = None or Lax

  • RequireSSL cookie attribute = True or False

Example:

Host - http://localhost:802/

Nectari Embedding - http://localhost:81/

 

HTTPS

  • Https host embedding https Nectari

  • Different or same domain name

  • SameSite cookie attribute = None or Lax

  • RequireSSL cookie attribute = True

Example:

Host - https://exampleerp.demo.com

Nectari Embedding - https://yourserver:81

 
Important  

When embedding Nectari into your ERP website using a Chromium-based browser, please ensure that your Web Client is bound through HTTPS rather than HTTP.