SESCOOKIE (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
m (remove displaytitle) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">SESCOOKIE cookie — Name of session cookie</span> | |||
<span class="pageSubtitle" | |||
<var>SESCOOKIE</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port | <var>SESCOOKIE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
Indicates the name of a cookie that will be used to maintain logical sessions that will be used to perform trusted logins for Janus port users who have just logged in through typical HTTP challenge-response mechanisms or through a $Sir_Login issued during <var>[[NEWSESCMD (JANUS DEFINE parameter)|NEWSESCMD]]</var> processing. This feature reduces the overhead of <var>NEWSESCMD</var> processing by limiting it to logical session establishment time, and it eliminates some of the idiosyncrasies of HTTP challenge-response authentication associated with password changes, whether end-user or system initiated. | Indicates the name of a cookie that will be used to maintain logical sessions that will be used to perform trusted logins for Janus port users who have just logged in through typical HTTP challenge-response mechanisms or through a $Sir_Login issued during <var>[[NEWSESCMD (JANUS DEFINE parameter)|NEWSESCMD]]</var> processing. This feature reduces the overhead of <var>NEWSESCMD</var> processing by limiting it to logical session establishment time, and it eliminates some of the idiosyncrasies of HTTP challenge-response authentication associated with password changes, whether end-user or system initiated. | ||
| Line 10: | Line 9: | ||
If both <var>SESCOOKIE</var> and <var>[[SSLSES (JANUS DEFINE parameter)|SSLSES]]</var> are specified, the session associated with the <var>SESCOOKIE</var> will be used in preference to the session associated with the SSL session, though these should almost always be the same. | If both <var>SESCOOKIE</var> and <var>[[SSLSES (JANUS DEFINE parameter)|SSLSES]]</var> are specified, the session associated with the <var>SESCOOKIE</var> will be used in preference to the session associated with the SSL session, though these should almost always be the same. | ||
<var>SESCOOKIE</var> is valid only for WEBSERV ports. | <var>SESCOOKIE</var> is valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | ||
==See also== | ==See also== | ||
Latest revision as of 23:11, 7 June 2016
SESCOOKIE cookie — Name of session cookie
SESCOOKIE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
Indicates the name of a cookie that will be used to maintain logical sessions that will be used to perform trusted logins for Janus port users who have just logged in through typical HTTP challenge-response mechanisms or through a $Sir_Login issued during NEWSESCMD processing. This feature reduces the overhead of NEWSESCMD processing by limiting it to logical session establishment time, and it eliminates some of the idiosyncrasies of HTTP challenge-response authentication associated with password changes, whether end-user or system initiated.
SESCOOKIE cookies are cryptographically designed to be virtually impossible to "fake".
If both SESCOOKIE and SSLSES are specified, the session associated with the SESCOOKIE will be used in preference to the session associated with the SSL session, though these should almost always be the same.
SESCOOKIE is valid only for WEBSERV ports.