Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vault init warning #66

Open
vrmerlin opened this issue Jun 5, 2020 · 0 comments
Open

Vault init warning #66

vrmerlin opened this issue Jun 5, 2020 · 0 comments

Comments

@vrmerlin
Copy link

vrmerlin commented Jun 5, 2020

This looks like a great approach to setting up a vault for Tomcat. I've got your solution working, with local customization, but am concerned about a warning I'm seeing.

When I initialize the vault with keytool, i'm getting the follow:

Warning:
The JCEKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore vault_data/vault.keystore -destkeystore vault_data/vault.keystore -deststoretype pkcs12".

The vault.sh tool (next step in initializing) works fine though.

If I do what the warning suggests and switch to pkcs12, then the vault.sh tool gives this error:

Exception encountered: java.lang.RuntimeException: Unable to get keystore ([vault_data/vault.keystore])

(yes, i've made some modifications to how the vault location works, but have it working fine with jceks)

Any way to get rid of that warning? Also, is the keystore configuration as you implemented it FIPS compliant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant