Logging and Analytics

The Nevis Access App offers the following logging capabilities.

HTTP User-Agent Based Logging and Analytics

The Nevis Access app uses a custom HTTP User-Agent header to report client information to the backend. You can use this information

• to gather statistical information about app usage, and/or
• to block access for specific devices or app/SDK versions.

The header contains the following information:

1. Name of the SDK (fixed to NMASDK)
2. SDK version including build number
3. Mobile device model
4. Operating system
5. OS version
6. Application bundle ID
7. Application version including build number

The header uses the following information order and format (the numbers in the code correspond with the numbers of the previous list):

Information Order

<1>/<2> (<3>; <4> <5>) <6>/<7>

Example User-Agent Header

NMASDK/1.6.0.5 (iPhone12,8; iPhoneOS 14.0) ch.nevis.accessapp/1.6.0.5

Parsing

You can use the following regular expression to extract individual parts from the User-Agent header:

User-Agent Parsing RegEx

^([\w\d\s]*)\/([\d.]*)\s\((.*);\s(.*)\)\s(.*)\/(.*)

Diagnostic Data

Nevis Authentication Cloud only

Only Access Apps using the Nevis Authentication Cloud backend are collecting diagnostic information.

The Nevis Access App collects diagnostic information and stores the data in the Nevis Authentication Cloud backend. The collection of diagnostic information serves to improve the authentication experience and performance as well as customer support purposes. Data is not collected to track individual users or individual user behaviour and is not shared outside Nevis.

An end user is able to opt-out of the diagnostic login via the settings screen.

For additional information refer to the Authentication Cloud documentation.