1. Its not an adobe issue, you have to install a c...
# adobe
1. Its not an adobe issue, you have to install a code signing certificate and then sign the code yourself. 1. Install a certificate, 2, run keytool -genkey -alias server -keyalg RSA -keysize 2048 -keystore mydemokeystore.jks 3. enter details as prompted, 4. keytool -certreq -alias server -file csr.csr -keystore mydemokeystore.jks 5, open up the csr in any of your favorite text editors and paste that in some ssl registers webite, 6, enter your credit card details as the whole SSL signing universe is a complete BS joke, 8. Once your "certified" key is generated download the certificate to your box. 9. Import the certificate keytool -import -trustcacerts -alias server -file YouCertificate.p7b -keystore mydemokeystore.jks 10 - Buy me a coffee https://cfml.slack.com/archives/C06TABBT8/p1651250316846529
You have to be kidding me ???? This is such crap. I'm not buying a SSL or any other tool to work on a Dev machine that I own. Does this mean Adobe is NOT GOING to fix this?
The file in question is the mod_jk.so file which was installed by Adobe. Here is the error message.
Sat Apr 30 083022.005077 2022] [so:error] [pid 51632] AH06665: No code signing authority for module at /private/etc/apache2/mod_jk.so specified in LoadModule directive.
Use a plain HTTP proxy in Apache and CF's built-in web server. The whole AJP/JK thing is pretty pointless, IMO, and it can restricts what HTTP verbs you use in REST APIs. We switched to HTTP proxy many years ago and it's so much simpler to work with and plenty fast enough.