-
Couldn't load subscription status.
- Fork 41.6k
No error message when server.ssl.keyAlias doesn't match an entry #19202
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
Conversation
...boot-project/spring-boot/src/test/java/org/springframework/boot/web/server/SslUtilsTest.java
Outdated
Show resolved
Hide resolved
| StepVerifier.create(result).expectNext("Hello World").verifyComplete(); | ||
| } | ||
|
|
||
| @Test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is no longer valid as the server will not even startup if its configured w/ an invalid alias.
|
Rebased to fix merge conflicts. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Thanks @Bono007. This has now been merged into master. |
If there is an invalid
ssl.server.key-aliasspecified (one that does not exist in the keystore) then the server will not startup.Closes gh-16168
NOTE Code was added to Netty, Tomcat, and Jetty but not to Tomcat as it already fails to startup in this case. I was going to add the code anyways so they all failed in the same manner but it became problematic getting a key store prior to the server starting up. I went ahead and left it alone.
NOTE Integration test cover each server in this scenario and I also verified all 4 servers manually in another consuming app.