|
Administrator
|
You get this during creating a CSR it seems. That s a validation rules of the relevant standards of that time --- RFC 1034 rules probably.
So, if you cannot use a wildcard, the safest (and most "compliant") path is to generate a CSR for the specific FQDN of the node.
But! if you are asking for a workaround, an idea; maybe you can bypass this CSR creating task. ( I m saying maybe:).. I mean changing the validator.
I mean you may use a different machine (having Java 8 -- a mature version of java 8),
and do those CSR things there and then import the resulting certificate here in EBS keystore, or alternatively you may do the entire tasks in that Java8, and then copy the resulting keystore, to EBS ..
But! I didn't try this. This may create compatibility problems. But if you want a thought experiment, then you got one:) Just saying.
|