If there is an invalid ssl.server.key-alias specified (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.
Comment From: onobc
Rebased to fix merge conflicts.
Comment From: onobc
Just pinging on this one as its been inactive for a bit.
Comment From: snicoll
@bono007 please don't do that. The issue has been triaged and has a milestone attached to it so it is effectively scheduled for resolution.
Comment From: onobc
Got it @snicoll . Then please excuse me in advance for the other issue I did the same thing on. Won't happen again.
On Sat, Jan 4, 2020, 4:20 AM Stéphane Nicoll notifications@github.com wrote:
@bono007 https://github.com/bono007 please don't do that. The issue has been triaged and has a milestone attached to it so it is effectively scheduled for resolution.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spring-projects/spring-boot/pull/19202?email_source=notifications&email_token=AG4RTQ6CHKEYYWXE67AGAULQ4BPINA5CNFSM4JTOKVB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICVAVA#issuecomment-570773588, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4RTQ3N3J3DIAWSORQQ7BLQ4BPINANCNFSM4JTOKVBQ .
Comment From: mbhave
Thanks @bono007. This has now been merged into master.