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-1021: 'Failed to add key Reason: Invalid license key, or the license key has expired.'

Centrify DirectControl ,   Centrify Identity Service, Mac Edition ,  

12 April,16 at 11:02 AM

Applies to: All versions of Centrify DirectControl / DirectManage Access Manager
 
Question:
When entering the license key into the Centrify admin console, the following messages may appear:
 
Failed to add key. Reason: Invalid license key, or the license key has expired.
 
(Or)
 
Failed to add a license key
Reason: Invalid license key, it has expired or this is a non-FIPS 140 key on a system that requires FIPS 140 keys
  
(Or)
 
This key is invalid.
Please ensure you are entering the correct key for the product you are using (a DirectAudit key on a DirectAudit console or a DirectControl key on the DirectControl console). It is also possible that this a non-FIPS 140 key on a system that requires FIPS 140 keys.
 
User-added image
 
 
 
What are some potential causes of these?
 
Answer:
The errors can appear if the following Windows Group Policy is set under the Active Directory domain: 
 
  Computer Configuration / Windows Settings / Security Settings / Local Policies / Security Options / "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing"
 
Note: Even after successfully entering the license key, re-enabling FIPS compliance will cause the license key to disappear and error message will show up again.
 
Centrify is FIPS compliant as of DirectControl 4.2, please request for FIPS compliant license keys if this needed in the environment.
 
If the above GP has been disabled, but the error is still shown, check the following registry keys to determine the true FIPS status:
 
Windows Server 2008, Windows Vista and above:
 
  HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled
 
 
Windows Server 2003, Windows XP:
 
  HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy
 
If this setting is enabled, the value is 1.
If this setting is disabled, the value is 0.
 
For more information, please see the Microsoft article at: (Provided as a courtesy)

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