Closed seanknox closed 8 years ago
Thanks for the report @seanknox. Looks like we want it to fail validation and return a 400 rather than throw an exception and a 500 server error.
Other option is to (maybe?) have it turn into an empty string in the database, but that's just off hand thought... Often when doing self signed certs I skip the CN but it isn't the worst requirement for us to keep either
@helgi @bacongobbler another thought: does the CN column really need the not-null constraint? if there's a app dependency somewhere on CN then perhaps the controller can reject SSL certs with blank CNs; otherwise let it be null.
I'm fairly certain that the router relies on the common name, so I'm not too sure it's a field that we can leave blank.
Hi fine Deis folks,
I'm using v2.4.1. I generated self-signed SSL certs as part of the Workflow guide to start testing. Appears that a cert with with a blank CN causes an error when the controller tries to save to the DB as the column has a not-null constraint. Generating another cert with CN worked fine. Logs are below, let me know if you need any additional information.
cheers, Sean