RADIUS Secret Limitations

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PAM Self-Hosted Articles
2 min read
L3 Networker
No ratings

Question

What are the limitations of a RADIUS shared secret when created by CAVaultManager?

Answer

RADIUS servers generally do not have restrictions with the shared secret used by clients. However, when creating a shared secret to be used by the vault for RADIUS authentication, the following are limitations:
 
* The shared secret should not contain the '^' character. If the '^' is necessary, then an extra '^' should be used as a negation. For example, if the shared secret on the RADIUS server is CyberArk^123, then the shared secret when created by CAVaultManager should be CyberArk^^123
* the shared secret can also not contain < or >
* the shared secret can not contain &

For full info please review the documentation here:
https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/11.3/en/Content/PASREF/Vault%20Specifications.h... Q: What are the limitations of a RADIUS shared secret when created by CAVaultManager
 
A: RADIUS servers generally do not have restrictions with the shared secret used by clients. However, when creating a shared secret to be used by the vault for RADIUS authentication, the following are limitations
 
* The shared secret should be 15 characters or less
* The shared secret should not contain the '^' character. If the '^' is necessary, then an extra '^' should be used as a negation. For example, if the shared secret on the RADIUS server is CyberArk^123, then the shared secret when created by CAVaultManager should be CyberArk^^123, being cognizant of the 15 character limitation
* the shared secret can also not contain < or >
Rate this article: