Edgewall Software

Changes between Version 2 and Version 4 of Ticket #11293


Ignore:
Timestamp:
Sep 7, 2013, 5:06:36 PM (11 years ago)
Author:
Ryan J Ollos
Comment:

rjollos.git:1c203a85 results in a ConfigurationError being raised immediately when tracopt.perm.authz_policy is enabled, and before any other steps are taken to configure the installation for authz permissions. It seems better to only raise the ConfigurationError when AuthzPolicy is in the list of active permission_policies. So the behavior I propose is, allow tracopt.perm.authz_policy to be enabled but don't perform any error checks unless AuthzPolicy is in the list of active permission_policies. Once AuthzPolicy is active, we are very strict about failing with a ConfigurationError if the authz policy won't be enforced due to a configuration error or dependency not being loaded. Furthermore, after #10285, if AuthzPolicy is active but tracopt.perm.authz_policy is not enabled, a ConfigurationError will be raised, and this also extends to the case of raising a ConfigurationError if a permission policy in permission_policies is misspelled.

In rjollos.git:t11293.2 another case is covered by raising a ConfigurationError if the authz_file is empty.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11293 – Release Notes

    v2 v4  
     1A `ConfigurationError` is raised if `tracopt.perm.authz_policy` is enabled and AuthzPolicy is in the list of active `permission_policies` but `ConfigObj` is not installed, or the `authz_file` option isn't set or the file is not found. The `ConfigObj` dependency for `tracopt.perm.authz_policy` is enforced in `setup.py`.