Skip to main content

 

Eptura Knowledge Center

OnGuard - Notes

  1. Last updated
  2. Save as PDF

OnGuard Verbose Logging

Our integration regularly checks the OnGuard version so we know the system is online. This enables us to notify the technical contacts you share with us so they are aware ASAP should the system go offline. 
You must ensure that OnGuard Verbose logging is not left active, as this generates many logs and could cause your OnGuard server to experience issues.

License Checking / Logging in to OnGuard

On setup, to connect to OnGuard via our Access Control Client, a valid user and license is required to create a connection. When an error is returned at any time, if the license expires or the user becomes invalid, for example, we will not continuously check it is valid or attempt to log in. We will check 5 times every 15 seconds before we no longer check for a valid license. 

Once an updated license has been applied in OnGuard or the user details updated in the client, the services should be restarted via the client under the "Status" tab and we will validate the license/user once again and then log in.

Segment ID

The Eptura Visitor integration can run on a specific segment in OnGuard. The required segment ID can be shared during deployment.

User Account

The user account details entered in the Eptura Visitor client to connect to OnGuard do not need to be associated with any Directory accounts and can simply be an Internal account. When using an Internal account, rules to enforce a 90 day password expiry and a limit of 5 password attempts may be in place. 

Non-directory account settings can be changed via the web interface Lenel application at https://localhost:8080/ on the Lenel server - the 90 day expiry 5 login attempt lockout may be disabled there.

Access Levels

OnGuard allows for access level names to be a maximum of 64 characters in length. This will need to be considered when applying our Custom or Company-based access features.