10/29/2022 0 Comments Handshaker windowsHere is an ascii representation of the Certification Path I see in Chrome/Windows:īootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_USįramework arguments: -product .jee.product -product .jee.product -product .jee.product -product .jee.productĬommand-line arguments: -os win32 -ws win32 -arch x86_64 -product .jee.product -product .jee.product -product .jee.product -data file:/E:/workspaces/neon/safeguards/ -product .jee.product We have our own certificates which, I suppose are self-signed, but we have our own CA which is trusted so in the browser, the connection is trusted. I'm experiencing the same issues as the last comment on but since that bug is marked RESOLVED, I figured I'd open a new one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |