4.14. Security 4.14.1. Realms 4.14.2. Users, groups, roles, and passwords 4.14.3. Passwords encryption 4.14.4. Managing authentication by key 4.14.5. RBAC 4.14.6. SecurityMBean 4.14.7. Security Schema and Deployer 5.14.3. Architecture 5.14.4. Available realm and login modules 5.14.5. Encryption service 5.14.6. Role discovery policies 5.14.7. Default role policies 5.15. Troubleshooting specifying a hostKeyPassword might require installing the BouncyCastle provider to support the desired encryption algorithm. • hostKeyPub is the location of the public key of the server. • sshRole is the default

ENCRYPTION SERVICE The EncryptionService is a service registered in the OSGi registry providing means to encrypt and check encrypted passwords. This service acts as a factory for Encryption objects objects actually performing the encryption. This service is used in all Karaf login modules to support encrypted passwords. Configuring properties Each login module supports the following additional set SECURITY FRAMEWORK 181 encryption.name Name of the encryption service registered in OSGi (cf. paragraph below) encryption.enabled Boolean used to turn on encryption encryption.prefix Prefix for encrypted

can also enable security transport on the cluster. Two modes are supported: * SSL: • Symmetric Encryption: Cellar provides additional discovery mechanisms, See Discovery Service (jclouds and kubernetes) 10.10.1.* encryption enabled="true"> 19 encryption> 5.1. Nodes identification When you installed the Cellar feature, your Karaf instance became

can also enable security transport on the cluster. Two modes are supported: • SSL: • Symmetric Encryption: Cellar provides additional discovery mechanisms, See Discovery Service (jclouds and kubernetes) 10.10.1.* encryption enabled="true"> 19 encryption> 5.1. Nodes identification When you installed the Cellar feature, your Karaf instance became