dbd_login_token

exec master..dbd_login_token @module sysname, @slot int, @pin sysname, @save bit

This procedure logs in to the token on the slot with user PIN. If login was successful and @save set to 1, login information is saved in registry for automatic login in the future. PIN is saved in encrypted form. Login is global and affects all user sessions. Once logged all connections get access to the token. If @save set to 0 SQL Server logs out from the token after restart.

PIN info is saved Windows User's registry. Two instances of SQL Server running under different Windows accounts will not be able to use PINs of each other. Two instances of SQL Server running under same Windows account will be able to use PINs of each other.

Login is not always required by token. Some tokens and it's keys may be configured to allow encryption without a login. DbDefence doesn't provide functions for key generation and token configuration.

To logout use dbd_logout_token

To list token keys dbd_list_token_keys