tracker issue : CF-4203359

select a category, or use search below
(searches all categories and all time range)
Title: not valid in MacOS 10.14 Mojave

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/ThirdParty

Reporter/Name(from Bugbase): e c / ()

Created: 09/27/2018

Components: Installation/Config, Connector

Versions: 2016,11.0,2018

Failure Type: Non Functioning

Found In Build/Fixed In Build: MacOS 10.14, CF 11,0,11,301867 / CF2016U11,CF2018U4

Priority/Frequency: Blocker / All users will encounter

Locale/System: English / Other

Vote Count: 18

Problem Description: created by CF 11 installation and setup, is not recognized as a valid file, and apache cannot start up with mod_jk connector to CF11 server

Steps to Reproduce:
Install CF11 Dev Edition on MacOS 10.14
Use external apache instance on the same machine as the CF11 install
Start up ColdFusion
Start up apache with mod_jk entries in httpd.conf that are inserted by CF11 install
run command to verify httpd.conf:
sudo apachectl

Actual Result:
error msg when running apachectl: invalid cert, not sign..
(I can dig up the original error msg, but i need to pull it off time machine from home)

Expected Result:
no error message, and apache should be able to start up without issue

Any Workarounds:
Revert back to 10.13 High Sierra, re-installed CF 11 using same dmg. No issues



This absolutely needs to be resolved.
Comment by Wil G.
29868 | October 28, 2018 07:41:36 PM GMT
So far Adobe's only response has been "Our development team is working on this bug and will soon release the fix for this issue. As of now, we don't have an ETA, as an when we will release the patch. So I would appreciate if you can work on the High Sierra OS for some time, meanwhile, we will release the patch." So basically do not upgrade your macOS because Adobe has failed to keep up with the times.
Comment by Wil G.
29887 | October 31, 2018 08:09:18 PM GMT
wow what a response you got from Adobe. I'm not surprised by that answer from them, because they haven't said shiat about it in this issue tracker thread. It's so sad that this issue has got me by the balls, so that I can't upgrade to Mojave for other reasons. I understand might be smaller nbr of users that have our type of setup, but how hard can it be to get this working with Mojave this entire time they had before Mojave went GA
Comment by e c.
29888 | October 31, 2018 08:47:51 PM GMT
Can we please get a fix on this.
Vote by Stephen C.
29944 | November 19, 2018 08:22:37 PM GMT
Any update? Or an ETA?
Vote by Bert D.
29999 | December 04, 2018 01:57:07 PM GMT
This issue is being fixed. Will update you once this is fixed.
Comment by Nitin K.
30003 | December 05, 2018 04:41:14 AM GMT
please fix ASAP
Vote by Felix P.
30035 | December 10, 2018 05:27:33 PM GMT
Nitin ... I assume if you fix it for this version of CF, you will also fix it for later versions of CF?
Comment by Kevin B.
30041 | December 11, 2018 07:58:29 PM GMT
I see this happening with CF2016 as well. Any idea when this will be fixed?
Comment by Randy J.
30055 | December 14, 2018 09:06:39 PM GMT
Apple states that, _“__Starting in iOS 8 and macOS 10.10, the system offers library validation as a policy for the dynamic libraries that a process links against. The policy is simple: A program may link against any library with the same team identifier in its code signature as the main executable, or with any Apple system library. Requests to link against other libraries are denied”._  __  So even though we have signed our file, it cannot be loaded with Apache’s main executable, since both have different Team IDs. We have filed a bug in Apple’s RADAR system. Apple will provide a patch for this problem through the update.   *As a workaround:* *You can disable inbuilt Apache and try installing Apache through Homebrew (Since Library Validation happens only for System Applications, this workaround will work). Alternatively you can compile & install Apache from source (*   Reference:  []
Comment by Nitin K.
30065 | December 17, 2018 01:38:03 PM GMT
This is critical for anyone doing development on a work (i.e., enterprise) that cannot download a separate apache instance for their local machine.
Vote by Phillip D.
30066 | December 17, 2018 04:21:10 PM GMT
The issue is logged with Apple in bug reporting tool (Radar). Bug #46769398. 
Comment by Nitin K.
30091 | January 07, 2019 06:58:15 AM GMT
is there a way to make the bug filed with Radar, visible to us? if not, please keep us updated regularly. We are chomping at the bit to get CF going with Mojave. thx
Comment by e c.
30094 | January 07, 2019 06:51:45 PM GMT
As per Apple, this will be fixed in OSX 10.14.4. The current version is 10.14.2. re-targeting to the next update.
Comment by Piyush K.
30104 | January 10, 2019 06:00:24 AM GMT
any news?
Comment by Riccardo K.
30114 | January 14, 2019 04:53:14 PM GMT
Still on target for the 10.14.4 release? I noticed that the Mojave page in the mac app store is now at 10.14.3
Comment by Randy J.
30136 | January 23, 2019 04:23:36 PM GMT
Mojave has been released for quite some time now. When will a fix this be released?
Comment by Patrick F.
30405 | February 27, 2019 10:49:37 PM GMT
As a paying customer with many installations I find it unacceptable that it's taken so far almost 6 months (macOS Mojave was released on September 2018) for this to be fixed. Our whole development team is still using the older version of macOS on oir dev machines just because of this one issue. I also find it very worry-some the fact that this happens with *every* release of macOS: CF is *always* behind and is up to us developers to find workaround by ourselves. It seems that the Coldfusion development team does *not* test CF against the macOS beta releases so they can have a version ready by the time the final version of macOS is released. This is *very* frustrating and is the #1 reason why we have been considering other alternatives to CF, as we feel the platform does not get the support it deserves from Adobe.
Comment by Jose E.
30407 | February 28, 2019 12:23:11 PM GMT
Jose, we're in the same boat too. We're thinking once we run out of mileage with CF11 (EOL or security flaw), we will probably move off of CF. Adobe had plenty of time to test CF out with Mojave before it was released. To me that indicates, Adobe treats CF as an afterthought, keep doors open and lights on, and expends the least amount of its energy in supporting the non-latest versions of CF server
Comment by e c.
30408 | February 28, 2019 03:16:19 PM GMT
How about installing a different copy of Apache? I've used the suggestion about using Homebrew to install a different copy of Apache and disabled the built in Apache. It's very simple. The simple matter of this is Apple broke this for EVERYONE! The PHP community is running into the same problem. Same for Apache Tomcat developers. Take it up with Apple.
Comment by Wil G.
30410 | February 28, 2019 07:17:37 PM GMT
FYI: This issue is fixed by Apple in latest Mojave 10.14.4 Beta release. 
Comment by Nitin K.
30424 | March 04, 2019 09:39:20 AM GMT
I have successfully installed CF2018 on the latest OS X 10.14.4 Beta.
Comment by Ricardo R.
30545 | March 20, 2019 10:16:33 PM GMT
OS X 14.4.4 has been released and I can confirm this works now.
Comment by Kevin B.
30575 | March 27, 2019 01:02:15 PM GMT
Also came to say that the OS X 14.4.4 patch has indeed fixed this issue.
Comment by Stephen C.
30576 | March 27, 2019 01:09:39 PM GMT