Has anyone been successful in deploying using an externally signed SSL?
I can get the extender to work fine with a self-signed cert but have had no luck using a cert signed by network solutions… As is typical the IBM documentation is sparse on specifics regarding the types of keys, bit length, etc… What I did was take the pfx file (2048 bit cert) (which includes the private key) and generate .cer and .key files using ssl:
The action to configure the extender runs fine and the services all start without incident, but the running BESiOSServer.exe process is NOT bound to 443 and of course there is no response.
The derby.log seems to have no decent information either.
I also noticed that when set up with a self signed cert, it’s a 1024 bit cert, whereas the cert from NetSol is 2048 (mandatory minimum)… not sure if that affects it at all.
On a hunch, I manually edited the cert and key PEM files and removed all extraneous data outside the BEGIN and END lines… I ran the configuration task with those new files and it works like a champ!