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-19016: The Centrify adinfo Command Reports an Invalid Connector

Authentication Service ,  

22 August,19 at 11:26 PM

Problem:
  
The Centrify command, adinfo -i cip, reports that invalid connectors are found in the domain.  The output is similar to:
  
  
Centrify Connectors invalid:
      Centrify Connector: w2k12r2s-cps041.single01.cdc
        Centrify Identity Platform URL:
        Connector Site:
        Connector FQDN: w2k12r2s-cps041.single01.cdc
        Tenant ID:
        Connector port: -
        Connector IWA HTTP port: -
        Connector IWA HTTPS port: -
    
  
The centrifydc.log file contains these messages:
  



adclient[8695]: DEBUG <bg-MAIN:refreshCloudConnectorsInfo> base.cloudconnector.locator got FQDN from parent object: w2k12r2s-cps041.single01.cdc
  
adclient[8695]: DEBUG <bg-MAIN:refreshCloudConnectorsInfo> base.cloudconnector.locator Invalid cloud connector SCP for cloudUrl:
  
adclient[8695]: INFO  <bg-MAIN:refreshCloudConnectorsInfo> base.cloudconnector.locator Centrify Agent will not use Centrify Connector 'w2k12r2s-cps041.single01.cdc' to provide connectivity to Centrify Identity Platform URL '' because keywords 'centrify.core.cloudurl' are missing.
 
Cause:

This issue occurs when Centrify connectors are in the same Active Directory domain with connectors from Idaptive.  The message is not an error.  There is no loss of functionality for the CDC agent.
  
Resolution:

The 19.6 Centrify DirectControl agent has a modified message indicating that the non-Centrify connector will be "skipped".  The logging level for this new message is changed to DEBUG.

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

Related Articles

 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? article[TIPS] A Centrify Server Suite Cheat Sheet articleKB-17161: Preparing for the Tenant URL Change to centrify.net articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin?