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: To Track//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 /

Priority/Frequency: Blocker / All users will encounter

Locale/System: English / Other

Vote Count: 13

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 Genovese
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 Genovese
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.
29944 | November 19, 2018 08:22:37 PM GMT
Any update? Or an ETA?
Vote by Bert Dawson
29999 | December 04, 2018 01:57:07 PM GMT
This issue is being fixed. Will update you once this is fixed.
Comment by Nitin Kumar
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 Benore
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 Johnson
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 Kumar
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 Duba
30066 | December 17, 2018 04:21:10 PM GMT