-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Tomcat fails to start when PEM files are used and key-store-password is not specified #31253
Comments
Thanks for the report. The problem is due to different defaults in Spring Boot and Tomcat when no password is configured. In Spring Boot, the entry is added to the in-memory Lines 93 to 96 in c996e43
In Tomcat, the default password for retrieving the key from the store is "changeit". It works when you configure any password as the entry is added to the store with that password and Tomcat then uses that same password when retrieving the key from the store. Jetty, Netty, and Undertow don't seem to be affected. |
key-store-password
is not specified
@wilkinsona Hi, can I please work on it? Kindly share if there is any other helpful insight with regards to this issue. |
Thanks for the offer, @shaheryarshakeel, but I already have a possible fix for this that I have been discussing with @scottfrederick. |
@wilkinsona Please let me know if I can help in any way, I genuinely wants to tap into open source contributions and there is no place better than spring which I use everyday, thanks |
Thanks for the offer, @shaheryarshakeel. Please keep an eye out for issues that are labeled as ideal for contribution. |
Spring Boot: 2.7.0
Web Server fails to start when PEM files with not password-protected key are used and
key-store-password
is not specified.However if any password is set in
key-store-password
, the app starts successfully.My expected behavior is that app start successully without
key-store-password
Exception's stacktrace
application.yml
Certificare and prvvate key are test-cert-chain.pem and test-key.pem .
pom.xml
DemoApplication.java
The text was updated successfully, but these errors were encountered: