SSLSES (JANUS DEFINE parameter): Difference between revisions
m (1 revision) |
m (remove displaytitle) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">Do trusted-logons for SSL session subsequent connections.</span> | |||
<span class="pageSubtitle" | |||
<var>SSLSES</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. | <var>SSLSES</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
Indicates that SSL (Secure Socket Layer) logical sessions will be used to perform trusted logins for Janus port users once they have performed a standard login through typical HTTP challenge-response mechanisms or through a [[$Sir_Login]] issued during <var>[[NEWSESCMD (JANUS DEFINE parameter)|NEWSESCMD]]</var> processing. | Indicates that SSL (Secure Socket Layer) logical sessions will be used to perform trusted logins for Janus port users once they have performed a standard login through typical HTTP challenge-response mechanisms or through a [[$Sir_Login]] issued during <var>[[NEWSESCMD (JANUS DEFINE parameter)|NEWSESCMD]]</var> processing. | ||
Latest revision as of 00:00, 8 June 2016
Do trusted-logons for SSL session subsequent connections.
SSLSES is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
Indicates that SSL (Secure Socket Layer) logical sessions will be used to perform trusted logins for Janus port users once they have performed a standard login 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. The feature also eliminates some of the idiosyncrasies of HTTP challenge-response authentication associated with password changes, whether end-user or system initiated.
The SSLSES parameter is designed for SSL server ports.
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.
SSLSES is valid only for WEBSERV ports.