- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-24-2025 08:20 AM
Hi Everyone,
We are experiencing an issue where password reconciliation for SQL accounts is failing. After investigation, we identified that the failures are caused by passwords starting with certain special characters, specifically
@(ampersand),
'(single quote), and
"(double quote).
Our goal is to ensure that generated passwords always start with an alphabetic character while still allowing “safe” special characters elsewhere in the password. Currently, using the
PasswordForbiddenChars setting in the platform will prevent the above special characters from appearing anywhere in the password, but it does not specifically restrict other special characters from being in the first position.
Is there a way to configure CyberArk to forbid special characters in the first position of a password while still allowing safe special characters in other positions to meet the password complexity requirements of our organization.
10-24-2025 08:26 AM
It was recently introduced .
AllowFirstCharSpecial
But it's version 14.6+
https://docs.cyberark.com/pam-self-hosted/14.6/en/content/pasref/automatic%20password%20management%20-%20generate%20password.htm
10-24-2025 08:30 AM
is there a way we can achieve it on older version? I am on 12.6
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

