data
folder there are several files. Two of the files contain secret keys generated on the server that must be protected and are utilized to encrypt and decrypt the end-user's auto-generated master passwords. There is also a .sql
file which contains a local cache of encrypted data. It is critical that access to this data folder is restricted.data
folder is under the SSO Connect install folder, typically $HOME/sso_connect/data
.data
folder is in C:\ProgramData\Keeper SSO Connect\data\
since v14.1. Prior to v14.1 it was in C:\Program Files\Keeper Security\SSO Connect\data\
.data/
folder.Java
libraries. On Linux the software is installed in /opt/cloudhsm
.cloudhsm_client
service is running in the background:HsmCredentials.properties
on the Java Classpath.
However, this may not work for some reason. Instead you may need to set HSM_USER
, HSM_PASSWORD
, and HSM_PARTITION
environment variables. For testing, you will probably have to set the shell variables.http://localhost:8080/config
sso_connect
, KeeperSSO
, or some similar name. The folder will contain many jar files.data
folder contains the SSO Connect configuration files. At a minimum it should be backed up after initial configuration and each time the configuration is modified. In addition to the configuration files, there are data files in data
but they will automatically be refreshed if they get out of synch with the Keeper server. Thus, regular periodic backups can be used but are not necessary. The data
folder on each SSO Connect instance needs to be backed up independently because not all of the configuration settings are shared among instances.data
folder is under the SSO Connect install folder, typically $HOME/sso_connect/data
.data
folder is in C:\ProgramData\Keeper SSO Connect\data\
since v14.1. Prior to v14.1 it was in C:\Program Files\Keeper Security\SSO Connect\data\
.data
folder as described above, restore it before starting SSO Connect. If a data
folder already exists (because you started SSO Connect), stop SSO Connect, remove all files in the data folder, copy the files from the backed-up data folder, and restart SSO Connect. SSO Connect should start successfully.data
folder or if the backup is out-of-date you will need to configure the replacement instance as if it were a new installation. Please follow the SSO Connect installation guide.data
folder. The HSM is accessed once, when SSO Connect starts, and also any time the configuration is changed. If the configuration files are encrypted and the encryption key stored on the HSM is lost or inaccessible the SSO Connect instance will need to be configured again in order to create new, unencrypted configuration files. Delete the contents of the data
folder and configure SSO Connect from scratch again.-disableSKS
command-line option.