Warning: This page has not been updated in over over a year and may be outdated or deprecated.
configuration:permission_options
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| configuration:permission_options [2017/08/30 14:53] – demiankatz | configuration:permission_options [2020/09/22 14:18] – demiankatz | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Permission Configuration ====== | ====== Permission Configuration ====== | ||
| - | VuFind 2.4 introduced a configurable permission system, allowing access to certain features of the system to be restricted based on a variety of options such as username, login status, IP address, etc. All of the available rules and permissions are documented in [[https:// | + | VuFind 2.4 introduced a configurable permission system, allowing access to certain features of the system to be restricted based on a variety of options such as username, login status, IP address, etc. All of the available rules and permissions are documented in [[https:// |
| - | VuFind 4.1 added another layer of configuration to the system: the ability to configure exactly what VuFind will do when a particular permission is denied. Permissions may be checked in either controllers or templates, and different options are available for denied permissions in each of these places. A controller may throw an exception or display a custom " | + | VuFind 4.1 added another layer of configuration to the system: the ability to configure exactly what VuFind will do when a particular permission is denied. Permissions may be checked in either controllers or templates, and different options are available for denied permissions in each of these places. A controller may throw an exception or display a custom " |
| + | VuFind 6.1 adds a significant new option to permissionBehavior.ini: | ||
| ===== Structure of permissionBehavior.ini ===== | ===== Structure of permissionBehavior.ini ===== | ||
| Line 129: | Line 130: | ||
| === Suppress tab outside of IP range === | === Suppress tab outside of IP range === | ||
| - | // You are using the PrimoCentral index and are offering it with a separate search tab. The user should be allowed to see the tab only if he is in a certain IP range. Otherwise the search tab should not get displayed. // | + | // You are using the PrimoCentral index and are offering it with a separate search tab. The user should be allowed to see the tab only if logged |
| config.ini: | config.ini: | ||
| Line 152: | Line 153: | ||
| === Show note outside of IP range === | === Show note outside of IP range === | ||
| - | // You are using the PrimoCentral index and are offering it with a separate search tab. Any user should be allowed to see the tab, but if the tab is clicked, the user should see a note telling him that he needs to be in a certain IP range to use this tab. // | + | // You are using the PrimoCentral index and are offering it with a separate search tab. Any user should be allowed to see the tab, but if the tab is clicked, the user should see a note telling him that he needs to be logged |
| config.ini and permissions.ini should be the same as the previous example. | config.ini and permissions.ini should be the same as the previous example. | ||
| Line 158: | Line 159: | ||
| permissionBehavior.ini: | permissionBehavior.ini: | ||
| [access.PrimoModule] | [access.PrimoModule] | ||
| - | deniedControllerBehavior = " | + | deniedControllerBehavior = " |
| === Throw exception outside of IP range === | === Throw exception outside of IP range === | ||
| - | // You are using the PrimoCentral index and are offering it with a separate search tab. Any user should be allowed to see the tab, but if the tab is clicked, the system should throw an exception. // | + | // You are using the PrimoCentral index and are offering it with a separate search tab. Any user should be allowed to see the tab, but if the tab is clicked, the system should throw an exception |
| config.ini and permissions.ini should be the same as the previous example. | config.ini and permissions.ini should be the same as the previous example. | ||
| Line 168: | Line 169: | ||
| permissionBehavior.ini: | permissionBehavior.ini: | ||
| [access.PrimoModule] | [access.PrimoModule] | ||
| - | deniedControllerBehavior = " | + | deniedControllerBehavior = " |
| ---- struct data ---- | ---- struct data ---- | ||
| ---- | ---- | ||
configuration/permission_options.txt · Last modified: 2023/11/09 19:10 by demiankatz