[Secure Vault] Security configuration file required when resolving already encrypted secrets
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
It is required to define the <APIM_HOME>/repository/conf/security/secret-conf.properties file, in order to enable Carbon level secure vault and provide other related configurations, when resolving already encrypted secrets.
keystore.identity.location=/home/wso2carbon/wso2am-3.2.0/repository/resources/security/internalKeyStore.jks
keystore.identity.type=JKS
keystore.identity.store.password=identity.store.password
keystore.identity.store.secretProvider=org.wso2.carbon.securevault.DefaultSecretCallbackHandler
secretRepositories.file.provider=org.wso2.securevault.secret.repository.FileBaseSecretRepositoryProvider
secretRepositories.file.location=repository/conf/security/cipher-text.properties
secretRepositories=file
secVault.enabled=true
keystore.identity.key.password=identity.key.password
carbon.secretProvider=org.wso2.securevault.secret.handler.SecretManagerSecretCallbackHandler
keystore.identity.key.secretProvider=org.wso2.carbon.securevault.DefaultSecretCallbackHandler
keystore.identity.alias=wso2carboninternal
Suggested Labels:
Type/Docs, Priority/Highest
Suggested Assignees:
@pubudu538 @tharindu1st
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked “Resolving already encrypted passwords during server startup” documentation page. Check whether it explains the requirement for <APIM_HOME>/repository/conf/security/secret-conf.properties and the provided settings; done means the page clearly documents the required configuration for resolving already encrypted secrets.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100