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-43281: Retrieving A Secret Throws the Error "Bad HTTP Request with status 500"

Privileged Access Service ,  

27 October,20 at 02:36 PM

Problem:
  
When retrieving a secret, the error popups, "Bad HTTP request with status 500."  Showing the error details gives this information:
  
User-added image
  

Cause:
  
This error appears when the secret's policy setting, Default Secret Challenge Profile, is set to "-Not Allowed".  The default policy can be seen by browsing to:
  
Resources -> Secrets -> <secret> -> Policy
  
User-added image
  
  
Resolution:
  
Modify the secret's policy such that the chosen profile allows the secret to be downloaded and/or viewed by the user.

Related Articles

 article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part III article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part II articleCentrify 20.6 Release Notes article[HOW TO] Use an OAuth2 application and PowerShell to programmatically get the contents of a secret article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I articleKB-2094: Failed to retrieve groups from provisioning source (1355) 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? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role?