Trust the local root CA it in Windows / MacOS.Generating the local root CA using OpenSSL.So, first of all, we already have our own certificate that’s self-signed on the local ABAP server – what’s missing is just Then use that certificate in your local web server. The best option: Generate your own certificate, either self-signed or signed by a local root, and trust it in your operating system’s trust store. While looking around for some ideas, I came across this page on Let’s Encrypt’s website – where it says and I quote below… The ABAP 1909 Developer Edition comes with a self-signed certificate that will technically serve “secure” HTTPS traffic for local development but browsers and even some API software/tools today frown upon self-signed certificates so much so that they labelled it as “Not secure” or just wouldn’t work with it – I am really over simplifying the reason here… To this on Safari in MacOS or Chrome in Windows….Īhhh…much better! A complete, no error valid SSL on a local ABAP dev server Introduction I’ll share in a few simple steps, how I was able to generate my own local root CA with OpenSSL and use that to sign the SSL certificate that comes delivered in ABAP 1909 Developer Edition (CN=*.dummy.nodomain) to get rid of the annoying browser warning messages when accessing any URLs served through HTTPS on this local ABAP development environment.Īnnoying browser error and SSL status that says Not secure TL DR: Resolve the ERR_CERT_AUTHORITY_INVALID issue on browsers with https using self-signed SSL certificate by generating your own local root CA (Certificate Authority) using OpenSSL on Windows/MacOS for ABAP 1909 Developer Edition for local development.
0 Comments
Leave a Reply. |