Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-2500: How to get Apache sub-version to work with Centrify Apache plugin?

Centrify DirectControl ,   Centrify DirectControl Plugins ,  

12 April,16 at 11:13 AM

Applies to: All versions of Centrify DirectControl for Applications.
 
Question:
 
How does one get the Apache sub-version client to use the AD credentials?
 
Answer:
 
If the Apache to front-end subversion is used, Centrify's Apache plugin module can be purchased.
 
Directions.
 
1) Edit the main Apache server configuration file, httpd.conf to include the appropriate Centrify DirectControl for Apache module in the Dynamic Shared Object section.
 
2) Any of the Centrify DirectControl shared object files can be added using the LoadModule directive. Be aware that the location of the modules to load is different depending on whether the 32-bit or 64-bit versions Apache is being run:
 
32-bit Apache: /usr/share/centrifydc/apache/lib
32-bit Apache: /usr/share/centrifydc/apache/lib64
 
Example:
 
  LoadModule centrifydc_auth_module /usr/share/centrifydc/apache/lib/mod_auth_centrifydc_20.so
 
However, the simplest way to add Centrify DirectControl to the Apache server is by using the Include directive and specifying the location of the default Centrify DirectControl for Apache configuration file for the version of Apache being used. The default Centrify DirectControl for Apache configuration files are located in the directory:
 
  /usr/share/centrifydc/apache/samples/conf 
 
Example:
 
  Include /usr/share/centrifydc/apache/samples/conf/centrify22.conf
 
See also: http://mail-archives.apache.org/mod_mbox/httpd-users/200902.mbox/%3C498F74B8.1060808@edsrd1.yzk.co.jp%3E
 
2) Please make sure subversion supports PAM, see: http://paulosman.me/2007/01/04/pam-authentication-for-apache-trac-and-svn.html
If PAM is used, the silent Kerberos authentication capabilities that come with Centrify's Apache plugin will be lost.
 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-3925: How to add Centrify parameter to a group policy articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-2359: How to configure a Kerberos based SSO solution in WebLogic & Oracles Http Server ( OHS) environment? articleKB-3318: QuickStart guide to setup the Centrify Apache HTTP SSO module. articleKB-2048 Configure Centrify DirectControl for cluster environment articleKB-7469: Missing Centrify Apache library for Solaris Sparc and 64 bit versions articleKB-1251: Apache Kerberos (SSO) authentication may not work after upgrading to DirectControl 4.2.x from a previous release