The <abbrtitle="Single Sign On">SSO</abbr> cookie is built 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>).
To edit <abbrtitle="Single Sign On">SSO</abbr> cookie parameters, go in Manager, <code>General Parameters</code>><code>Cookies</code>:
</p>
<ul>
<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>
</li>
<liclass="level1"><divclass="li"><strong>Multiple domains</strong>: enable <ahref="cda.html"class="wikilink1"title="documentation:2.0:cda">cross domain mechanism</a> (without this, you cannot extend <abbrtitle="Single Sign On">SSO</abbr> to other domains)</div>
<liclass="level2"><divclass="li"><strong>Non secured cookie</strong>: the cookie can be sent over HTTP and HTTPS connections</div>
</li>
<liclass="level2"><divclass="li"><strong>Secured cookie</strong>: the cookie can only be sent over HTTPS</div>
</li>
<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>: same as double cookie but only one session is created in session database</div>
<liclass="level1"><divclass="li"><strong>Javascript protection</strong>: set httpOnly flag, to prevent cookie from being 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 means it will be destroyed when browser is closed. You can change this behavior by setting a cookie expiration time. It must be an integer. <strong>Cookie Expiration Time</strong> value is a number of seconds until the cookie expires. Set a zero value to disable expiration time and use a session cookie.</div>
<divclass="notewarning">When you change cookie expiration time, it is written on the user hard disk unlike session cookie
</div><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.
Portal <abbrtitle="Uniform Resource Locator">URL</abbr> is the address used to redirect users on the authentication portal by:
</p>
<ul>
<liclass="level1"><divclass="li"><strong>Handler</strong>: user is redirected if he has no <abbrtitle="Single Sign On">SSO</abbr> cookie (or in <ahref="cda.html"class="wikilink1"title="documentation:2.0:cda">CDA</a> mode)</div>
</li>
<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>
</li>
</ul>
<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.