| Table of Contents | ||||
|---|---|---|---|---|
|
...
Whenever adding or editing an API permission, the API key will be randomly generated and disabled from User modifications. Users can select the Read and Write access in various sections like 'Services', 'Equipment', 'Service Desk', and 'SNMP'. This Grid allows the User to 
, 
, or 
API Key Permissions.
Permissions Tab
...
Select the desired 'API Permission' and set any desired Expiration Date. Depending on API Endpoint, you will see fields for granting Read and Write permissions.
Edit
Users can an existing API Permission if there are problems with the initial configuration.
Delete
Users can
an existing API Permission. Care should be exercised in this action to make sure that the Permission is not being used elsewhere by PCR-360.
...
From 'API Users' Grid the User is able to ,
to
, 
, or
API Keys associated to a User's Session.
...
From 'API Tokens' Grid the User is able to API Keys Tokens associated to a User's Session. This is very useful if somehow an API Token becomes compromised and another User begins using the Token as well; an Admin User can immediately remove the Token and force all Users of that API Key to re-authenticate, rather than having to wait for the Token to expire.
...
The system configuration AUTH_SESSION_LIFETIME_SECONDS defines the length of time a Session is valid. If this parameter is set to "0", then the Session is set to not expire as long as the User. Any other value to cause the User to need to get a new Token after the defined interval, regardless of User Activity.
The system configuration AUTH_SESSION_ACTIVITY_SECONDS defined the length of time a User's Session is valid, before it times out do to Inactivity.
For more detail on these configuration values, please see the Authentication Configuration Wiki Page.
...