Timeline for What is the proper setup procedure for SSL Tunnel certificates?
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 25, 2015 at 12:51 | vote | accept | abiessu | ||
Aug 25, 2015 at 12:51 | answer | added | abiessu | timeline score: 0 | |
Aug 25, 2015 at 0:15 | comment | added | abiessu | @k1DBLITZ: thank you for the suggestion. I can dig in to the Java keystore in each of the systems, although I think I've covered this by having the customer's trusted root certificate placed in all systems trust stores within Niagara. But I will double-check the next time I'm at that site. The main question I'm asking here is whether there is some sort of special setup involved for the certificates themselves (file format, etc.) that supports or at least helps the https tunnel process within a web browser environment... | |
Aug 24, 2015 at 21:14 | comment | added | k1DBLITZ | Just a hunch.... but Niagara use a Java framework if I'm not mistaken. Which means it's likely this subsystem that fails to work is using the Java Keystore, which will not contain the trusted root of the customers CA. Combining the cert chain is a workaround. You might try going down the path of importing the customer's root into the java keystore.... or.. it may end up being a waste of time. :) Sorry, I have no direct experience with Niagara. | |
Aug 21, 2015 at 19:03 | review | First posts | |||
Aug 21, 2015 at 19:04 | |||||
Aug 21, 2015 at 18:55 | comment | added | abiessu | Also, attempting to supply both public and private keys from cert A within the PEM for cert C fails with error "Can't import multiple private keys from one file" | |
Aug 21, 2015 at 18:48 | history | asked | abiessu | CC BY-SA 3.0 |