The <abbrtitle="Single Sign On">SSO</abbr> cookie is build by the portal (as described in the <ahref="../../documentation/presentation.html#login"class="wikilink1"title="documentation:presentation">login kinematic</a>), or by the Handler for cross domain authentication (see <ahref="../../documentation/presentation.html#cross_domain_authentication_cda"class="wikilink1"title="documentation:presentation">CDA kinematic</a>).
<liclass="level1"><divclass="li"><strong>Cookie name</strong>: name of the cookie, can be changed to avoid conflicts with other LemonLDAP::NG installations</div>
</li>
<liclass="level1"><divclass="li"><strong>Domain</strong>: validity domain for the cookie (the cookie will not be sent on other domains)</div>
<liclass="level2"><divclass="li"><strong>Double cookie</strong>: two cookies are delivered, one for HTTP and HTTPS connections, the other for HTTPS only</div>
<liclass="level2"><divclass="li"><strong>Double cookie for single session</strong>: as same, two cookies are delivered, but only one session is written in session database</div>
</li>
</ul>
</li>
<liclass="level1"><divclass="li"><strong>Javascript protection</strong>: set httpOnly flag, to avoid cookie been caught by javascript code</div>
<liclass="level1"><divclass="li"><strong>Cookie expiration time</strong>: by default, <abbrtitle="Single Sign On">SSO</abbr> cookie is a session cookie, which mean it will be destroyed when the browser is closed. You can change this behavior and set a cookie duration, for example:</div>
<liclass="level2"><divclass="li"><strong>+30s</strong>: 30 seconds from session creation</div>
</li>
<liclass="level2"><divclass="li"><strong>+10m</strong>: ten minutes from session creation</div>
</li>
<liclass="level2"><divclass="li"><strong>+1h</strong>: one hour from session creation</div>
</li>
<liclass="level2"><divclass="li"><strong>+3M</strong>: three months from session creation</div>
</li>
<liclass="level2"><divclass="li"><strong>+10y</strong>: ten years from session creation</div>
</li>
<liclass="level2"><divclass="li"><strong>Thursday, 25-Apr-1999 00:40:33 GMT</strong>: at the indicated time and date (but this is probably a bad idea)</div>
</li>
</ul>
</li>
</ul>
<p>
<p><divclass="notewarning">When you change cookie expiration time, it is written on the user hard disk unlike session cookie
<p><divclass="noteimportant">Changing the domain value will not update other configuration parameters, like virtual host names, portal <abbrtitle="Uniform Resource Locator">URL</abbr>, etc. You have to update them by yourself.
<liclass="level1"><divclass="li"><strong>Handler</strong>: user is redirected if he has no <abbrtitle="Single Sign On">SSO</abbr> cookie (or in <ahref="../../documentation/2.0/cda.html"class="wikilink1"title="documentation:2.0:cda">CDA</a> mode)</div>
<liclass="level1"><divclass="li"><strong>Portal</strong>: the portal redirect on itself in many cases (credentials POST, <abbrtitle="Security Assertion Markup Language">SAML</abbr>, etc.)</div>
<p><divclass="notewarning">The portal <abbrtitle="Uniform Resource Locator">URL</abbr><strong>must</strong> be inside <abbrtitle="Single Sign On">SSO</abbr> domain. If secured cookie is enabled, the portal <abbrtitle="Uniform Resource Locator">URL</abbr><strong>must</strong> be HTTPS.