WEBLOGCOOKIE (JANUS DEFINE parameter): Difference between revisions
(Created page with "{{DISPLAYTITLE:WEBLOGCOOKIE}} <span class="pageSubtitle"><section begin="desc" />cookie-name<section end="desc" /></span> WEBLOGCOOKIE is a parameter on JANUS DEFINE, which ...") |
(Automatically generated page update) |
||
| (12 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">WEBLOGCOOKIE cookie-name — Log user with web cookie ID</span> | |||
<span class="pageSubtitle"> | |||
WEBLOGCOOKIE is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port | <var>WEBLOGCOOKIE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
This parameter indicates that, for public URLs, Janus Web should log the user in with the userid specified by cookie-name. Normally, all public URL logins use the default public userid (usually WEBUSER). This parameter simply allows applications to set their own public userids. One way to do this is with the Janus Web API function [[$Web_Set_Cookie]]. | |||
If you specify the <var>WEBLOGCOOKIE</var> parameter, use caution if you also use the <var>[[WEBPUBLOG (JANUS DEFINE parameter)|WEBPUBLOG]]</var> parameter. <var>WEBPUBLOG</var> logins use CCASTAT or an external authorizer for public logins, therefore if a login cookie specifies a userid which has system privileges, a security breach is possible. For this reason, use of <var>WEBLOGCOOKIE</var> with <var>WEBPUBLOG</var> is not recommended, but it is not explicitly prohibited. | |||
If you specify the WEBLOGCOOKIE parameter, use caution if you also use the WEBPUBLOG parameter. WEBPUBLOG logins use CCASTAT or an external authorizer for public logins, therefore if a login cookie specifies a userid which has system privileges, a security breach is possible. For this reason, use of WEBLOGCOOKIE with WEBPUBLOG is not recommended, but it is not explicitly prohibited. | |||
Note that some browsers do not support cookies (though most do) and end-users can turn off support of the cookies feature. An end-user using a browser that does not support cookies or has their support turned off will be logged in using the default public userid (usually WEBUSER). | Note that some browsers do not support cookies (though most do) and end-users can turn off support of the cookies feature. An end-user using a browser that does not support cookies or has their support turned off will be logged in using the default public userid (usually WEBUSER). | ||
Public logins | Public logins that use a <var>WEBLOGCOOKIE</var> cookie will participate in web logging. | ||
Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | |||
See | ==See also== | ||
<ul> | |||
<li>[[List of Janus commands]] | |||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | |||
</ul> | |||
[[Category:JANUS DEFINE parameters|WEBLOGCOOKIE]] | [[Category:JANUS DEFINE parameters|WEBLOGCOOKIE]] | ||
Latest revision as of 22:28, 16 April 2013
WEBLOGCOOKIE cookie-name — Log user with web cookie ID
WEBLOGCOOKIE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter indicates that, for public URLs, Janus Web should log the user in with the userid specified by cookie-name. Normally, all public URL logins use the default public userid (usually WEBUSER). This parameter simply allows applications to set their own public userids. One way to do this is with the Janus Web API function $Web_Set_Cookie.
If you specify the WEBLOGCOOKIE parameter, use caution if you also use the WEBPUBLOG parameter. WEBPUBLOG logins use CCASTAT or an external authorizer for public logins, therefore if a login cookie specifies a userid which has system privileges, a security breach is possible. For this reason, use of WEBLOGCOOKIE with WEBPUBLOG is not recommended, but it is not explicitly prohibited.
Note that some browsers do not support cookies (though most do) and end-users can turn off support of the cookies feature. An end-user using a browser that does not support cookies or has their support turned off will be logged in using the default public userid (usually WEBUSER).
Public logins that use a WEBLOGCOOKIE cookie will participate in web logging.
Valid only for WEBSERV ports.