Greetings, We have Cosign configured on multiple CentOS 6.x servers with Apache 2.2 which all work fine. We recently stood up a new CentOS 7 box with Apache 2.4 and I’m having trouble getting Cosign to behave.
What I’ve done: * Installed Cosign module from source using the 3.3 branch (which has Apache 2.4 patch) found here: https://github.com/lhoekenga/cosign. That seemed to build fine. * Did all the other standard Cosign setup (filters directory, certs installed, etc.). * Module seems to be loaded fine as I see it in the list when I dod apachectl -M. Also, the error_log shows this line: [:notice] [pid 10331] mod_cosign: version INTERNAL initialized. That’s consistent with what we see on working machines except those typically show the version number, rather than INTERNAL. This is a very vanilla box with not much installed yet and I’m just trying to protect one Location as a test, so it’s a very simple config. When I hit a protected Location, I get a 500 Internal Server Error. The ssl_error_log shows this: [Wed Apr 22 15:07:43.033429 2015] [authn_core:error] [pid 27461] [client 128.118.87.68:63390] AH01796: AuthType Cosign configured without corresponding module Anyone seen this? Any suggestions? jd Joe DeLuca Web Manager Penn State Eberly College of Science ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
