Data Store Changes

Data changes made in the Administration Web Interface, the Tcl Command-Line Administration tool application, or a SOAP administration client do not require a restart of the OneSpan Authentication Server service to take effect straight away. Such changes are applied by OneSpan Authentication Server, and as such can immediately update any cached data.

In addition, when multiple OneSpan Authentication Server instances are replicating database changes to each other, they update their cached data as changes are replicated.

If the date/time or time zone is changed on the machine where OneSpan Authentication Server is installed, authentications will fail until the OneSpan Authentication Server service is restarted.

Cached data

The following data modifications relate to cached data:

• Creating, editing, and deleting policy records
• Creating, editing, and deleting client records
• Creating, editing, and deleting back-end server records
• Creating, editing, and deleting OneSpan Authentication Server records
• Creating, editing, and deleting domain records

These modifications will not take effect until the caches re-load the data automatically, in the following cases:

• Multiple OneSpan Authentication Server instances are sharing a database. In this case, only the OneSpan Authentication Server instance with which the data change is made will update its caches.
• Multiple OneSpan Authentication Server instances with their own database each are used, but they are not synchronized using replication.
• Direct modifications are made to the database, for example with an SQL tool or using Data Migration Tool (DMT).

Note that direct modifications to the database are not replicated to any other OneSpan Authentication Server instances – the same modifications must be made to the database of each instance (or the whole database is copied).

When multiple OneSpan Authentication Server instances are used, with multiple databases, user-configured synchronization between the databases must be considered. An OneSpan Authentication Server instance will not "know" about any data change made in another OneSpan Authentication Server instance's database until that change has been copied to its own database.

Automatic re-loading of cached data

In OneSpan Authentication Server, all cached data is periodically re-loaded from the data store. This time period, around 15 minutes, is tracked for each entry separately. Therefore, even without a restart, data changes will typically take effect within a matter of minutes (unless synchronization between databases is slower).