Question:

How does file re-authentication work, and can it be customised?

Answer:

By default, once a file is successfully authenticated, it undergoes seamless automatic background re-authentication if it remains in use for more than 8 hours, and then every subsequent 8 hours.  This process does not require user interaction.

This means that once a file is authenticated, it can stay open until the next re-authentication window, which is set for every 8 hours, as long as the user remains authorised. 

However, this re-authentication interval can be customised using the Advanced feature in the settings.  By setting it to re-authenticate every hour, file access will be re-evaluated within that one-hour timeframe.  If a user's account is disabled or removed, or if the job is deactivated, access will be denied at the next authentication interval of one hour.

Re-authenticate Every [x] Hours

This option allows the asset owner to enforce re-authentication every specified number of hours.  Once the designated timeout period is reached, access to the content will be re-authenticated.  Re-authentication triggers the creation of an audit record, so decreasing the time between re-authentication requests will increase the number of audit records generated for file access.

Additionally, you can opt to require a password prompt instead of automatic background re-authentication by using the following setting:

Disable Automatic Background Authentication

This setting disables automatic background authentication and requires the end user to re-enter the content password after the file cache timeout period has been reached. 

For more information, please refer to the MediaSeal Encryptor Manual.