Skip to main content
Home

Search form

Menu

Search form

  • SkyVault 2.0 overview
  • Video tutorials
  • Using SkyVault 2.0
  • System path conventions
  • Setting up authentication and security
    • SkyVault security
    • Managing SkyVault keystores
      • Keystore configuration
      • Keystore generation
      • Keystore key registration
      • Encrypted node properties
    • Cryptographic password hashing
    • Encrypting properties
    • Authentication subsystems
    • SkyVault authentication chain
    • Managing authentication directories
    • Authorities
    • Defining permissions
    • Access Control Lists
    • Modifying access control
    • Public services
    • Implementation and services
    • Admin password in default authentication
    • Security policies and filters
  • Content modeling with Model Manager
  • Copyright
  • You are here

    SkyVault 2.0 » Configuring » Setting up authentication and security » Managing SkyVault keystores

    Keystore key registration

    The keystore keys are registered with the repository to ensure that they are not accidentally changed.

    During bootstrap and JMX keystore reload and re-encryption operations, the repository checks if the main keystore's keys and the metadata key have changed. If they have changed, the repository throws an exception.

    Parent topic: Managing SkyVault keystores

    © 2017 TBS-LLC. All Rights Reserved.    Follow @twitter