JANUS WEB ALLOW - Revision history

Dme: /* Syntax */

2019-07-02T02:13:08Z

Syntax

← Older revision		Revision as of 02:13, 2 July 2019
Line 20:		Line 20:
	<p>		<p>
	This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.		This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
	Formerly, the rule was <code>JANUS WEB <i>portname</i> ALLOW *</code>, which allowed access to any user and did not require a login. </p>		Formerly, the rule was <code>JANUS WEB <i>portname</i> ALLOW </code>, which allowed access to any user and did not require a login. To restore that functionality, use the '1' bit of the <var>[[WEBDFLT parameter\|WEBDFLT]]</var> parameter to establish <code>ALLOW </code> as the default for non-SSL ports.</p>
	<p>		<p>
	For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:		For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:

JAL: update ALLOW rule default

2017-02-10T22:05:45Z

update ALLOW rule default

← Older revision		Revision as of 22:05, 10 February 2017
Line 14:		Line 14:
	If the <var>JANUS WEB ALLOW</var> command is specified with '''no''' optional parameters, it indicates that '''all''' users can have access to URLs that match the pattern in <var class="term">url</var>, and that requests for such public URLs are to be run under the explicit or default <var>WEBUSER</var> value from the port definition.		If the <var>JANUS WEB ALLOW</var> command is specified with '''no''' optional parameters, it indicates that '''all''' users can have access to URLs that match the pattern in <var class="term">url</var>, and that requests for such public URLs are to be run under the explicit or default <var>WEBUSER</var> value from the port definition.

	For non-SSL ports, the default <var>ALLOW/DISALLOW</var> rule as of Model 204 7.7 (~~and~~ 7.6 ~~maintenance~~), is:		For non-SSL ports, the default <var>ALLOW/DISALLOW</var> rule as of Model 204 7.7 zap 77Z088 (or 7.6 zap 76Z418), is:

	<p class="code">JANUS WEB <i>portname</i> ~~ALLOW * USER~~ *		<p class="code">JANUS WEB <i>portname</i> DISALLOW *
	</p>		</p>
			<p>
	This rule ~~means that all URLs are public but require~~ a ~~login~~. Formerly,		This rule requires a system administrator to explicitly define <var>ALLOW</var> rules to enable users to access non-SSL ports.
	the rule was <code>JANUS WEB <i>portname</i> ALLOW *</code>, which did not require a login.		Formerly, the rule was <code>JANUS WEB <i>portname</i> ALLOW *</code>, which allowed access to any user and did not require a login. </p>
			<p>
	For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:		For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:
			</p>
	<p class="code">JANUS WEB <i>portname</i> DISALLOW *		<p class="code">JANUS WEB <i>portname</i> DISALLOW *
	JANUS WEB <i>portname</i> ALLOW * USER <i>user</i>		JANUS WEB <i>portname</i> ALLOW * USER <i>user</i>

JAL: change ALLOW * to ALLOW * USER * for non-SSL

2016-12-29T19:26:25Z

change ALLOW * to ALLOW * USER * for non-SSL

← Older revision		Revision as of 19:26, 29 December 2016
Line 14:		Line 14:
	If the <var>JANUS WEB ALLOW</var> command is specified with '''no''' optional parameters, it indicates that '''all''' users can have access to URLs that match the pattern in <var class="term">url</var>, and that requests for such public URLs are to be run under the explicit or default <var>WEBUSER</var> value from the port definition.		If the <var>JANUS WEB ALLOW</var> command is specified with '''no''' optional parameters, it indicates that '''all''' users can have access to URLs that match the pattern in <var class="term">url</var>, and that requests for such public URLs are to be run under the explicit or default <var>WEBUSER</var> value from the port definition.

	For non-SSL ports, the default <var>ALLOW/DISALLOW</var> rule~~, which means that all URLs are public~~, is:		For non-SSL ports, the default <var>ALLOW/DISALLOW</var> rule as of Model 204 7.7 (and 7.6 maintenance), is:

	<p class="code">JANUS WEB <i>portname</i> ALLOW *		<p class="code">JANUS WEB <i>portname</i> ALLOW * USER *
	</p>		</p>

			This rule means that all URLs are public but require a login. Formerly,
			the rule was <code>JANUS WEB <i>portname</i> ALLOW *</code>, which did not require a login.

	For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:		For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:

JAL: /* Syntax */ misc formatting

2016-12-20T16:24:16Z

Syntax: misc formatting

← Older revision		Revision as of 16:24, 20 December 2016
Line 16:		Line 16:
	For non-SSL ports, the default <var>ALLOW/DISALLOW</var> rule, which means that all URLs are public, is:		For non-SSL ports, the default <var>ALLOW/DISALLOW</var> rule, which means that all URLs are public, is:

	<p class="code">JANUS WEB portname ALLOW *		<p class="code">JANUS WEB <i>portname</i> ALLOW *
	</p>		</p>

	For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:		For SSL ports, the default <var>ALLOW/DISALLOW</var> rules are:

	<p class="code">JANUS WEB portname DISALLOW *		<p class="code">JANUS WEB <i>portname</i> DISALLOW *
	JANUS WEB portname ALLOW * USER user		JANUS WEB <i>portname</i> ALLOW * USER <i>user</i>
	</p>		</p>

	where <var class="term">user</var> is the ~~userid~~ of the user that defined the port.		where <var class="term">user</var> is the user ID of the user that defined the port.

	<p class="note">'''Note:''' In no case is there a default rule for the PUT '''method''' value, which means that a PUT is not allowed unless explicitly permitted with a <var>JANUS WEB ALLOW</var> rule. </p>		<p class="note">'''Note:''' In no case is there a default rule for the PUT '''method''' value, which means that a PUT is not allowed unless explicitly permitted with a <var>JANUS WEB ALLOW</var> rule. </p>
Line 33:		Line 33:
	<tr><th><var>USER</var> user</th>		<tr><th><var>USER</var> user</th>

	<td>A user is allowed access to <var class="term">url</var> if he or she provides a ~~userid~~ and corresponding password for a ~~userid~~ that matches the pattern in <var class="term">user</var>. For example, if <var class="term">user</var> is <code>HOMER</code>, a user that logs in as <code>HOMER</code> will be allowed access to <var class="term">url</var>. If <var class="term">user</var> is string <code>.SIMP*</code>, a user that logs in as any ~~userid~~ that begins with "SIMP" will be allowed access to <var class="term">url</var>.		<td>A user is allowed access to <var class="term">url</var> if he or she provides a user ID and corresponding password for a user ID that matches the pattern in <var class="term">user</var>. For example, if <var class="term">user</var> is <code>HOMER</code>, a user that logs in as <code>HOMER</code> will be allowed access to <var class="term">url</var>. If <var class="term">user</var> is string <code>.SIMP*</code>, a user that logs in as any user ID that begins with "SIMP" will be allowed access to <var class="term">url</var>.
	<p>		<p>
	A <var class="term">user</var> value of asterisk () indicates that any valid <var class="product">Model 204</var> login will allow access to <var class="term">url</var>. This is particularly useful if <var class="term">url</var> is processed by an APSY subsystem, in which case <code>USER </code> forces a <var class="product">Model 204</var> login, but it leaves access decisions to APSY. </p>		A <var class="term">user</var> value of asterisk () indicates that any valid <var class="product">Model 204</var> login will allow access to <var class="term">url</var>. This is particularly useful if <var class="term">url</var> is processed by an APSY subsystem, in which case <code>USER </code> forces a <var class="product">Model 204</var> login, but it leaves access decisions to APSY. </p>
Line 40:		Line 40:

	<tr><th nowrap><var>USGROUP</var> usgroup</th>		<tr><th nowrap><var>USGROUP</var> usgroup</th>
	<td>A user will be allowed access to <var class="term">url</var> if he or she provides a ~~userid~~ and corresponding password for a user in the user group identified by <var class="term">usgroup</var>. User groups are defined with the <var>[[JANUS DEFINEUSGROUP]]</var> command.		<td>A user will be allowed access to <var class="term">url</var> if he or she provides a user ID and corresponding password for a user in the user group identified by <var class="term">usgroup</var>. User groups are defined with the <var>[[JANUS DEFINEUSGROUP]]</var> command.
	<p>		<p>
	The <var>USGROUP</var> parameter cannot be specified if the <var>USER</var> parameter is specified. It is valid to specify neither <var>USER</var> nor <var>USGROUP</var>. If neither is specified, and a user is allowed access to <var class="term">url</var> on the basis of the rest of the <var>ALLOW</var> rule, the request runs under the <var>WEBUSER</var> user ID taken from the port definition.</p></td></tr>		The <var>USGROUP</var> parameter cannot be specified if the <var>USER</var> parameter is specified. It is valid to specify neither <var>USER</var> nor <var>USGROUP</var>. If neither is specified, and a user is allowed access to <var class="term">url</var> on the basis of the rest of the <var>ALLOW</var> rule, the request runs under the <var>WEBUSER</var> user ID taken from the port definition.</p></td></tr>

JAL: typo

2016-09-22T20:43:22Z

typo

← Older revision		Revision as of 20:43, 22 September 2016
Line 75:		Line 75:
	<li>If the field is not present, it is considered a logon error, and <var class="product">Janus Web Server</var> returns a standard error page to the browser, or it runs the <var>LOGONERR</var> rule (described in [[JANUS WEB exception rules]]).</li>		<li>If the field is not present, it is considered a logon error, and <var class="product">Janus Web Server</var> returns a standard error page to the browser, or it runs the <var>LOGONERR</var> rule (described in [[JANUS WEB exception rules]]).</li>

	<li>If the field is present, it is used as a new password for the user. If the new password is accepted, <var class="product">Janus Web Server</var> attempts to run the <var>JANUS WEB</var> rule <var>NEWPASSWORD</var>. If no such rule is present, it returns an "Unauthorized," unless the port is defined with a <var>[[NEWPASSWORDC (JANUS DEFINE parameter)\|NEWPASSWORDC]]</var> parameter, in which case, processing simply continues for the posted URL.,/li>		<li>If the field is present, it is used as a new password for the user. If the new password is accepted, <var class="product">Janus Web Server</var> attempts to run the <var>JANUS WEB</var> rule <var>NEWPASSWORD</var>. If no such rule is present, it returns an "Unauthorized," unless the port is defined with a <var>[[NEWPASSWORDC (JANUS DEFINE parameter)\|NEWPASSWORDC]]</var> parameter, in which case, processing simply continues for the posted URL.</li>
	</ul>		</ul>

JAL: misc formatting

2016-09-22T20:41:04Z

misc formatting

← Older revision		Revision as of 20:41, 22 September 2016
Line 33:		Line 33:
	<tr><th><var>USER</var> user</th>		<tr><th><var>USER</var> user</th>

	<td>~~Indicates that a~~ user is allowed access to <var class="term">url</var> if he or she provides a userid and corresponding password for a userid that matches the pattern in <var class="term">user</var>. For example, if <var class="term">user</var> is <code>HOMER</code>, a user that logs in as <code>HOMER</code> will be allowed access to <var class="term">url</var>. If <var class="term">user</var> is string <code>.SIMP*</code>, a user that logs in as any userid that begins with "SIMP" will be allowed access to <var class="term">url</var>.		<td>A user is allowed access to <var class="term">url</var> if he or she provides a userid and corresponding password for a userid that matches the pattern in <var class="term">user</var>. For example, if <var class="term">user</var> is <code>HOMER</code>, a user that logs in as <code>HOMER</code> will be allowed access to <var class="term">url</var>. If <var class="term">user</var> is string <code>.SIMP*</code>, a user that logs in as any userid that begins with "SIMP" will be allowed access to <var class="term">url</var>.
	<p>		<p>
	A <var class="term">user</var> value of asterisk () indicates that any valid <var class="product">Model 204</var> login will allow access to <var class="term">url</var>. This is particularly useful if <var class="term">url</var> is processed by an APSY subsystem, in which case <code>USER </code> forces a <var class="product">Model 204</var> login, but it leaves access decisions to APSY. </p>		A <var class="term">user</var> value of asterisk () indicates that any valid <var class="product">Model 204</var> login will allow access to <var class="term">url</var>. This is particularly useful if <var class="term">url</var> is processed by an APSY subsystem, in which case <code>USER </code> forces a <var class="product">Model 204</var> login, but it leaves access decisions to APSY. </p>
Line 40:		Line 40:

	<tr><th nowrap><var>USGROUP</var> usgroup</th>		<tr><th nowrap><var>USGROUP</var> usgroup</th>
			<td>A user will be allowed access to <var class="term">url</var> if he or she provides a userid and corresponding password for a user in the user group identified by <var class="term">usgroup</var>. User groups are defined with the <var>[[JANUS DEFINEUSGROUP]]</var> command.
	<td>~~Indicates that a~~ user will be allowed access to <var class="term">url</var> if he or she provides a userid and corresponding password for a user in the user group identified by <var class="term">usgroup</var>. User groups are defined with the <var>[[JANUS DEFINEUSGROUP]]</var> command.
	<p>		<p>
	The <var>USGROUP</var> parameter cannot be specified if the <var>USER</var> parameter is specified. It is valid to specify neither <var>USER</var> nor <var>USGROUP</var>. If neither is specified, and a user is allowed access to <var class="term">url</var> on the basis of the rest of the <var>ALLOW</var> rule, the request runs under the <var>WEBUSER</var> user ID taken from the port definition.</p></td></tr>		The <var>USGROUP</var> parameter cannot be specified if the <var>USER</var> parameter is specified. It is valid to specify neither <var>USER</var> nor <var>USGROUP</var>. If neither is specified, and a user is allowed access to <var class="term">url</var> on the basis of the rest of the <var>ALLOW</var> rule, the request runs under the <var>WEBUSER</var> user ID taken from the port definition.</p></td></tr>

	<tr><th><var>IPADDR</var> ipaddr</th>		<tr><th><var>IPADDR</var> ipaddr</th>
	<td>~~Indicates that a~~ user on a machine with an IP address that matches <var class="term">ipaddr</var> is allowed access to <var class="term">url</var>. <var class="term">ipaddr</var> can be an IPV4 dotted-decimal address, an IPV6 address (as of version 7.7 of Model 204), or it can be a subnet.		<td>A user on a machine with an IP address that matches <var class="term">ipaddr</var> is allowed access to <var class="term">url</var>. <var class="term">ipaddr</var> can be an IPV4 dotted-decimal address, an IPV6 address (as of version 7.7 of Model 204), or it can be a subnet.

	IPV4 subnets are indicated by an IP address followed by one of these:		<ul>
			<li>IPV4 subnets are indicated by an IP address followed by one of these:
	<ul>		<ul>
	<li>A forward slash (<tt>/</tt>) followed by a netmask (with no intervening blanks)</li>		<li>A forward slash (<tt>/</tt>) followed by a netmask (with no intervening blanks)</li>
Line 56:		Line 56:
	<p>		<p>
	For example, <code>198.242.244.97</code> is a simple IP address that must be matched exactly. <code>.198.242.244.0/255.255.255.0</code>, which is equivalent to <code>198.242.244.0-24</code>, indicates that any machine on subnet 198.242.244.0 is to be allowed access to <var class="term">url</var>. </p>		For example, <code>198.242.244.97</code> is a simple IP address that must be matched exactly. <code>.198.242.244.0/255.255.255.0</code>, which is equivalent to <code>198.242.244.0-24</code>, indicates that any machine on subnet 198.242.244.0 is to be allowed access to <var class="term">url</var>. </p>

			<li>IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,
			<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>.
	<p>		<p>
	~~IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,~~		An IPV6 subnet is indicated by the first address in the range, followed by a forward slash, and a decimal value equal to the number of bits in the network prefix. A subnet that includes the example address above is: <code>fe80::200:0/48</code>. </p></li>
	~~<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>. </p>~~		</ul>
	~~<p>~~
	An IPV6 subnet is indicated by the first address in the range, followed by a forward slash, and a decimal value equal to the number of bits in the network prefix. A subnet that includes the example address above is: <code>fe80::200:0/48</code>.
	</p>
	<p>		<p>
	The <var>IPADDR</var> parameter cannot be specified if the <var>IPGROUP</var> parameter is specified. It is valid to specify neither <var>IPADDR</var> nor <var>IPGROUP</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPADDR</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPADDR</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>		The <var>IPADDR</var> parameter cannot be specified if the <var>IPGROUP</var> parameter is specified. It is valid to specify neither <var>IPADDR</var> nor <var>IPGROUP</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPADDR</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPADDR</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>

	<tr><th><var>IPGROUP</var> ipgroup</th>		<tr><th><var>IPGROUP</var> ipgroup</th>
	<td>~~Indicates that a~~ user on a machine with an IP address that is in <var class="term">ipgroup</var> is allowed access to <var class="term">url</var>. IP address groups are defined with the <var>[[JANUS DEFINEIPGROUP]]</var> command.		<td>A user on a machine with an IP address that is in <var class="term">ipgroup</var> is allowed access to <var class="term">url</var>. IP address groups are defined with the <var>[[JANUS DEFINEIPGROUP]]</var> command.
	<p>		<p>
	The <var>IPGROUP</var> parameter cannot be specified if the <var>IPADDR</var> parameter is specified. It is valid to specify neither <var>IPGROUP</var> nor <var>IPADDR</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPGROUP</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPGROUP</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>		The <var>IPGROUP</var> parameter cannot be specified if the <var>IPADDR</var> parameter is specified. It is valid to specify neither <var>IPGROUP</var> nor <var>IPADDR</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPGROUP</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPGROUP</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>

	<tr><th nowrap><div id="newpassf"></div><var>NEWPASSF</var> fieldname <br>\| <var>NEWPASSF2</var> fieldname</th>		<tr><th nowrap><div id="newpassf"></div><var>NEWPASSF</var> fieldname <br>\| <var>NEWPASSF2</var> fieldname</th>
	<td>~~Indicates that a~~ POST for the specified URL will have its posted form fields scanned for a form field called <var class="term">fieldname</var>:		<td>An HTTP POST for the specified URL will have its posted form fields scanned for a form field called <var class="term">fieldname</var>:
	<ul>		<ul>
	<li>If the field is not present, it is considered a logon error, and <var class="product">Janus Web Server</var> returns a standard error page to the browser, or it runs the <var>LOGONERR</var> rule (described in [[JANUS WEB exception rules]]).</li>		<li>If the field is not present, it is considered a logon error, and <var class="product">Janus Web Server</var> returns a standard error page to the browser, or it runs the <var>LOGONERR</var> rule (described in [[JANUS WEB exception rules]]).</li>

JAL: add IPV6 address format

2016-09-19T21:16:02Z

add IPV6 address format

← Older revision		Revision as of 21:16, 19 September 2016
Line 46:		Line 46:

	<tr><th><var>IPADDR</var> ipaddr</th>		<tr><th><var>IPADDR</var> ipaddr</th>
	<td>Indicates that a user on a machine with an IP address that matches <var class="term">ipaddr</var> is allowed access to <var class="term">url</var>. <var class="term">ipaddr</var> can be ~~a simple IP~~ address, or it can be a subnet. ~~Subnets~~ are indicated by an IP address followed by ~~either~~ of these:		<td>Indicates that a user on a machine with an IP address that matches <var class="term">ipaddr</var> is allowed access to <var class="term">url</var>. <var class="term">ipaddr</var> can be an IPV4 dotted-decimal address, an IPV6 address (as of version 7.7 of Model 204), or it can be a subnet.

			IPV4 subnets are indicated by an IP address followed by one of these:
	<ul>		<ul>
	<li>A forward slash (<tt>/</tt>) followed by a netmask (with no intervening blanks)</li>		<li>A forward slash (<tt>/</tt>) followed by a netmask (with no intervening blanks)</li>
	<li>A hyphen (<tt>-</tt>) followed by a number of bits in the subnet mask (with no intervening blanks)</li>
			<li>A hyphen (<tt>-</tt>) followed by the number of bits in the subnet mask (with no intervening blanks)</li>
	</ul>		</ul>
	<p>		<p>
	For example, <code>198.242.244.97</code> is a simple IP address that must be matched exactly. <code>.198.242.244.0/255.255.255.0</code>, which is equivalent to <code>198.242.244.0-24</code>, indicates that any machine on subnet 198.242.244.0 is to be allowed access to <var class="term">url</var>. </p>		For example, <code>198.242.244.97</code> is a simple IP address that must be matched exactly. <code>.198.242.244.0/255.255.255.0</code>, which is equivalent to <code>198.242.244.0-24</code>, indicates that any machine on subnet 198.242.244.0 is to be allowed access to <var class="term">url</var>. </p>
			<p>
			IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,
			<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>. </p>
			<p>
			An IPV6 subnet is indicated by the first address in the range, followed by a forward slash, and a decimal value equal to the number of bits in the network prefix. A subnet that includes the example address above is: <code>fe80::200:0/48</code>.
			</p>
	<p>		<p>
	The <var>IPADDR</var> parameter cannot be specified if the <var>IPGROUP</var> parameter is specified. It is valid to specify neither <var>IPADDR</var> nor <var>IPGROUP</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPADDR</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPADDR</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>		The <var>IPADDR</var> parameter cannot be specified if the <var>IPGROUP</var> parameter is specified. It is valid to specify neither <var>IPADDR</var> nor <var>IPGROUP</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPADDR</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPADDR</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>

JAL: typo

2016-09-15T23:37:10Z

typo

← Older revision		Revision as of 23:37, 15 September 2016
Line 52:		Line 52:
	</ul>		</ul>
	<p>		<p>
	For example, <code>198.~~244~~.244.97</code> is a simple IP address that must be matched exactly. <code>.198.242.244.0/255.255.255.0</code>, which is equivalent to <code>198.242.244.0-24</code>, indicates that any machine on subnet 198.242.244.0 is to be allowed access to <var class="term">url</var>. </p>		For example, <code>198.242.244.97</code> is a simple IP address that must be matched exactly. <code>.198.242.244.0/255.255.255.0</code>, which is equivalent to <code>198.242.244.0-24</code>, indicates that any machine on subnet 198.242.244.0 is to be allowed access to <var class="term">url</var>. </p>
	<p>		<p>
	The <var>IPADDR</var> parameter cannot be specified if the <var>IPGROUP</var> parameter is specified. It is valid to specify neither <var>IPADDR</var> nor <var>IPGROUP</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPADDR</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPADDR</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>		The <var>IPADDR</var> parameter cannot be specified if the <var>IPGROUP</var> parameter is specified. It is valid to specify neither <var>IPADDR</var> nor <var>IPGROUP</var>. If neither is specified, the rule makes no restrictions on the basis of IP address. If <var>IPADDR</var> and <var>USER</var> or <var>USGROUP</var> is specified, a user must satisfy both the <var>IPADDR</var> criterion and the <var>USER</var> or <var>USGROUP</var> criterion to be allowed access to <var class="term">url</var>.</p></td></tr>

JAL: remove displaytitle

2016-01-27T20:46:48Z

remove displaytitle

Show changes

JAL at 23:28, 26 February 2013

2013-02-26T23:28:27Z

← Older revision		Revision as of 23:28, 26 February 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:JANUS WEB ALLOW}}		{{DISPLAYTITLE:JANUS WEB ALLOW}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Permit access to a web port~~<section end="desc" />~~</span>		<span class="pageSubtitle">Permit access to a web port</span>

	The JANUS WEB ALLOW command indicates that a request from a particular user or set of users can have access to any URL that matches a specified pattern (the '''url''' value).		The JANUS WEB ALLOW command indicates that a request from a particular user or set of users can have access to any URL that matches a specified pattern (the '''url''' value).
Line 6:		Line 6:
	==Syntax==		==Syntax==

	<p class="syntax"~~><section begin="syntax" /~~> JANUS WEB portname ALLOW [method] url -		<p class="syntax">JANUS WEB portname ALLOW [method] url -
	[USER user \| USGROUP usgroup] -		[USER user \| USGROUP usgroup] -
	[IPADDR ipaddr \| IPGROUP ipgroup] -		[IPADDR ipaddr \| IPGROUP ipgroup] -
	[[NEWPASSF \| NEWPASSF2] fieldname]		[[NEWPASSF \| NEWPASSF2] fieldname]
	~~<section end="syntax" />~~</p>		</p>
	<p class="caption">JANUS WEB ALLOW command syntax		<p class="caption">JANUS WEB ALLOW command syntax
	</p>		</p>