$Web User - Revision history

JAL: /* Syntax */

2013-06-05T21:56:43Z

Syntax

← Older revision		Revision as of 21:56, 5 June 2013
Line 5:		Line 5:

	==Syntax==		==Syntax==
	<p class="syntax">%bruser = $Web_User		<p class="syntax"><span class="term">%bruser</span> = $Web_User
	</p>		</p>

	<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.		<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.

	==Usage notes==		==Usage notes==

JALWiccan: Automatically generated page update

2013-04-10T18:18:32Z

Automatically generated page update

← Older revision		Revision as of 18:18, 10 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:$Web_User}}		{{DISPLAYTITLE:$Web_User}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>User ID sent by browser~~<section end="desc" />~~</span>		<span class="pageSubtitle">User ID sent by browser</span>

	<var>$Web_User</var> returns the userid that was sent by the browser in the HTTP user authentication header ("Authorization"), which could be different from the current <var class="product">Model 204</var> userid.		<var>$Web_User</var> returns the userid that was sent by the browser in the HTTP user authentication header ("Authorization"), which could be different from the current <var class="product">Model 204</var> userid.

	==Syntax==		==Syntax==
	<p class="syntax"~~><section begin="syntax" /~~>%bruser = $Web_User		<p class="syntax">%bruser = $Web_User
	~~<section end="syntax" />~~</p>		</p>

	<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.		<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.

JAL at 22:09, 26 October 2012

2012-10-26T22:09:14Z

← Older revision		Revision as of 22:09, 26 October 2012
Line 10:		Line 10:
	<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.		<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.

	The most likely use for <var>$Web_User</var> is in a LOGONERR exception handler ([[JANUS WEB exception rules\|"JANUS WEB exception rules"]]) or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.		==Usage notes==
			<ul>
			<li>The most likely use for <var>$Web_User</var> is in a LOGONERR exception handler ([[JANUS WEB exception rules\|"JANUS WEB exception rules"]]) or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.

			<li>For non-public, that is, logon required URLs, <var>$Web_User</var> will equal $USERID if HTTP user authentication is used. But it might be null or even a different userid, if NEWSESCMD is used to do some other kind of user authentication, such as certificate-based authentication. For public URLs, <var>$Web_User</var> might be null or it might contain the last userid that the browser used to log on for the port. Since a browser does not know which URLs for a port are public or private, it will usually send a userid and password for every URL on a port after a successful login.

			<li>While <var>$Web_User</var> can be used in any code, its most common use is likely to be in [[JANUS WEB exception rules\|exception rules]], especially those associated with logon processing, such as LOGONERR and NEWPASSWORD rules, or in NEWSESCMD processing.
			</ul>

			==Example==
	The following example from a LOGONERR exception handler stores a record in a file for a failed logon attempt.		The following example from a LOGONERR exception handler stores a record in a file for a failed logon attempt.

Line 25:		Line 33:
	END STORE		END STORE
	</p>		</p>

	For non-public, that is, logon required URLs, <var>$Web_User</var> will equal $USERID if HTTP user authentication is used. But it might be null or even a different userid, if NEWSESCMD is used to do some other kind of user authentication, such as certificate-based authentication. For public URLs, <var>$Web_User</var> might be null or it might contain the last userid that the browser used to log on for the port. Since a browser does not know which URLs for a port are public or private, it will usually send a userid and password for every URL on a port after a successful login.

	While <var>$Web_User</var> can be used in any code, its most common use is likely to be in exception rules (), especially those associated with logon processing, such as LOGONERR and NEWPASSWORD rules, or in NEWSESCMD processing.

	==See also==		==See also==
	<ul>		<ul>
	<li>[[$Web_Password]]</var>		<li><var>[[$Web_Password]]</var>
	</ul>		</ul>

	[[Category:Janus Web Server $functions\|$Web_User]]		[[Category:Janus Web Server $functions\|$Web_User]]

JAL at 21:55, 26 October 2012

2012-10-26T21:55:23Z

← Older revision		Revision as of 21:55, 26 October 2012
Line 5:		Line 5:

	==Syntax==		==Syntax==
	<p class="syntax"><section begin="syntax" />%~~BRUSER~~ = $Web_User		<p class="syntax"><section begin="syntax" />%bruser = $Web_User
	<section end="syntax" /></p>		<section end="syntax" /></p>

	<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.		<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.

	The most likely use for <var>$Web_User</var> is in a LOGONERR exception handler () or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.		The most likely use for <var>$Web_User</var> is in a LOGONERR exception handler ([[JANUS WEB exception rules\|"JANUS WEB exception rules"]]) or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.

	The following example from a LOGONERR exception handler stores a record in a file for a failed logon attempt.		The following example from a LOGONERR exception handler stores a record in a file for a failed logon attempt.

	<p class="code"> %BRUSER = $Web_User		<p class="code">%BRUSER = $Web_User
	%BRIPADDR = $Web_IPAddr		%BRIPADDR = $Web_IPAddr
	%TIME = $Web_Date		%TIME = $Web_Date

	IN FILE SECLOG STORE RECORD		IN FILE SECLOG STORE RECORD
	RECTYPE = 'LOGONERR'		RECTYPE = 'LOGONERR'
	TIME = %TIME		TIME = %TIME
	USER = %BRUSER		USER = %BRUSER
	IPADDR = %BRIPADDR		IPADDR = %BRIPADDR
	END STORE		END STORE
	</p>		</p>

Line 30:		Line 30:
	While <var>$Web_User</var> can be used in any code, its most common use is likely to be in exception rules (), especially those associated with logon processing, such as LOGONERR and NEWPASSWORD rules, or in NEWSESCMD processing.		While <var>$Web_User</var> can be used in any code, its most common use is likely to be in exception rules (), especially those associated with logon processing, such as LOGONERR and NEWPASSWORD rules, or in NEWSESCMD processing.

	See also [[$Web_Password]].		==See also==
			<ul>
			<li>[[$Web_Password]]</var>
			</ul>

	[[Category:Janus Web Server $functions\|$Web_User]]		[[Category:Janus Web Server $functions\|$Web_User]]

JALWiccan: 1 revision

2012-10-24T22:28:43Z

1 revision

← Older revision	Revision as of 22:28, 24 October 2012
(No difference)

JALWiccan: 1 revision

2012-10-24T22:28:26Z

1 revision

← Older revision		Revision as of 22:28, 24 October 2012
Line 5:		Line 5:

	==Syntax==		==Syntax==
	<p class="syntax"><section begin="syntax" /> %BRUSER = $Web_User		<p class="syntax"><section begin="syntax" />%BRUSER = $Web_User
	<section end="syntax" /></p>		<section end="syntax" /></p>

JALWiccan: 1 revision

2012-10-18T22:43:17Z

1 revision

← Older revision	Revision as of 22:43, 18 October 2012
(No difference)

JALWiccan: 1 revision

2012-10-18T22:43:10Z

1 revision

← Older revision		Revision as of 22:43, 18 October 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />User ID sent by browser<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />User ID sent by browser<section end="desc" /></span>

	$Web_User returns the userid that was sent by the browser in the HTTP user authentication header ("Authorization"), which could be different from the current <var class="product">Model 204</var> userid.		<var>$Web_User</var> returns the userid that was sent by the browser in the HTTP user authentication header ("Authorization"), which could be different from the current <var class="product">Model 204</var> userid.

	==Syntax==		==Syntax==
Line 8:		Line 8:
	<section end="syntax" /></p>		<section end="syntax" /></p>

	$Web_User takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.		<var>$Web_User</var> takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.

	The most likely use for <var>$Web_User</var> is in a LOGONERR exception handler () or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.		The most likely use for <var>$Web_User</var> is in a LOGONERR exception handler () or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.

JALWiccan: 1 revision

2012-10-18T21:53:33Z

1 revision

← Older revision	Revision as of 21:53, 18 October 2012
(No difference)

JALWiccan: 1 revision

2012-10-18T21:53:28Z

1 revision

← Older revision		Revision as of 21:53, 18 October 2012
Line 10:		Line 10:
	$Web_User takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.		$Web_User takes no arguments, and it returns a null indicating that the browser sent no userid, or it returns the userid sent by the browser.

	The most likely use for $Web_User is in a LOGONERR exception handler () or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.		The most likely use for <var>$Web_User</var> is in a LOGONERR exception handler () or in NEWSESCMD processing. Since a LOGONERR exception handler runs under the WEBUSER userid, $USERID will not indicate the userid for which the login failed. Also, NEWSESCMD processing runs under the PRELOGINUSER userid, so, again, $USERID will not return the userid sent in the HTTP headers by the browser.

	The following example from a LOGONERR exception handler stores a record in a file for a failed logon attempt.		The following example from a LOGONERR exception handler stores a record in a file for a failed logon attempt.
Line 26:		Line 26:
	</p>		</p>

	For non-public, that is, logon required URLs, $Web_User will equal $USERID if HTTP user authentication is used. But it might be null or even a different userid, if NEWSESCMD is used to do some other kind of user authentication, such as certificate-based authentication. For public URLs, $Web_User might be null or it might contain the last userid that the browser used to log on for the port. Since a browser does not know which URLs for a port are public or private, it will usually send a userid and password for every URL on a port after a successful login.		For non-public, that is, logon required URLs, <var>$Web_User</var> will equal $USERID if HTTP user authentication is used. But it might be null or even a different userid, if NEWSESCMD is used to do some other kind of user authentication, such as certificate-based authentication. For public URLs, <var>$Web_User</var> might be null or it might contain the last userid that the browser used to log on for the port. Since a browser does not know which URLs for a port are public or private, it will usually send a userid and password for every URL on a port after a successful login.

	While $Web_User can be used in any code, its most common use is likely to be in exception rules (), especially those associated with logon processing, such as LOGONERR and NEWPASSWORD rules, or in NEWSESCMD processing.		While <var>$Web_User</var> can be used in any code, its most common use is likely to be in exception rules (), especially those associated with logon processing, such as LOGONERR and NEWPASSWORD rules, or in NEWSESCMD processing.

	See also [[$Web_Password]].		See also [[$Web_Password]].

	[[Category:Janus Web Server $functions\|$Web_User]]		[[Category:Janus Web Server $functions\|$Web_User]]