MSIR.0826 NONPRE doesn't make sense for DISALLOW: Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
(Automatically generated page update) |
||
| Line 3: | Line 3: | ||
If the intent was to remove privileges granted to non-pre-compiled requests via a previous <tt>SIRMETH ALLOW</tt> command, the <tt>SIRMETH ALLOW</tt> command should be re-issued without the <tt>NONPRE</tt> keyword, or a <tt>SIRMETH ALLOW</tt> command should be issued without the <tt>NONPRE</tt> keyword for the subset of the subsystems for which privileges are to be removed from non-pre-compiled requests. See the ''Janus SOAP Reference Manual'' for more information about the <tt>SIRMETH</tt> command. | If the intent was to remove privileges granted to non-pre-compiled requests via a previous <tt>SIRMETH ALLOW</tt> command, the <tt>SIRMETH ALLOW</tt> command should be re-issued without the <tt>NONPRE</tt> keyword, or a <tt>SIRMETH ALLOW</tt> command should be issued without the <tt>NONPRE</tt> keyword for the subset of the subsystems for which privileges are to be removed from non-pre-compiled requests. See the ''Janus SOAP Reference Manual'' for more information about the <tt>SIRMETH</tt> command. | ||
[[Category:Sirius Mods | [[Category:Sirius Mods messages]] | ||
Revision as of 18:00, 19 April 2013
A SIRMETH DISALLOW command was issued with a NONPRE qualifier on a subsystem name. Since non-pre-compiled requests in a subsystem have no privileges to set globals, it doesn't make sense to disallow it.
If the intent was to remove privileges granted to non-pre-compiled requests via a previous SIRMETH ALLOW command, the SIRMETH ALLOW command should be re-issued without the NONPRE keyword, or a SIRMETH ALLOW command should be issued without the NONPRE keyword for the subset of the subsystems for which privileges are to be removed from non-pre-compiled requests. See the Janus SOAP Reference Manual for more information about the SIRMETH command.