System login
When a user attempts to login into the system, the local user database is always consulted first.
If the account is not found in the local DB, if Radius is enabled, a Radius Access Request is performed.
Access accounting
After a successful login, an accounting record is always created in the local database.
If Radius is enabled, an Radius Accounting Request is performed, but Unimus doesn't check the success or failure of this request.
This is done because event logins using the local database are accounted against Radius (if Radius is enabled).
If Unimus didn't allow login after Radius accounting failed, system access would not be possible in case of Radius failure.
An accounting record in the local DB is always created, so this mechanism does not compromise the auditability of the system access.