Permissions overview
Permission | Request header | Description |
|---|---|---|
|
| These are strictly necessary to call the module |
|
| These are not necessary, but if present, the module may do some extra operations (for example, show sensitive data about a patron) |
|
| Permissions granted to a module, which it can make use of, when making further calls to other modules. |
|
| Additional permissions granted by Okapi itself. Used only between Okapi and the authorization module, in some special situations, like when a moduleDescriptor has a "redirect" routing entry and also module-specific permissions. |
|
| The permissions a module expressed interest in, and which were granted to this user. Can be used for modifying the way a module behaves. |
|
| The name of the tenant |
|
| A JWT token given to a user after authentication |
|
| Tells the URL where the modules may contact Okapi, for making requests to other modules. Can be set on Okapi's command line when starting up. |
|
| Will be added to the responses from Okapi, to help debugging where the request actually went, and how long did it take. |
|
| The user Id of logged-in user. |
|
| Identifies the original request to Okapi. Useful for logging. |
|
| JWT tokens specifically made for invoking given modules.Used only between Okapi and the authorization module. |
| |
|