- 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.
11-01-2024 08:15 AM
We have few accounts where CPM is not assigned to the safe and we practice bringing password from somewhere and store in CA with proper password policies. The issue we have been facing is that whenever users change the password, they are not able to change the password in the vault even though password meets required password policy set in the platform.
The below error gets produced -- EPVWF061E The password typed does not adhere to current password policy rule
I have pasted our Current Policies setting below: What could be the other reasons which may be causing not to store password even though it meets password complexity defined in the platform?
PolicyID BOSTON-CYBERARK
PolicyName BOSTON-CYBERARK
SearchForUsages No
PolicyType Regular
ImmediateInterval 5
Interval 1440
MaxConcurrentConnections 3
AllowedSafes .*
MinValidityPeriod 60
ResetOveridesMinValidity Yes
ResetOveridesTimeFrame Yes
Timeout 90
UnlockIfFail No
UnrecoverableErrors 8800
MaximumRetries 5
MinDelayBetweenRetries 90
DllName CyberArk.Extensions.AWS.dll
ExeName CANetPluginInvoker.exe
XMLFile Yes
AllowManualChange Yes
PerformPeriodicChange No
HeadStartInterval 5
FromHour -1
ToHour -1
ChangeNotificationPeriod -1
DaysNotifyPriorExpiration 7
RCAllowManualReconciliation Yes
RCAutomaticReconcileWhenUnsynched No
RCReconcileReasons 8801,8802,8803
RCFromHour -1
RCToHour -1
NFNotifyPriorExpiration No
NFPriorExpirationRecipients
NFNotifyOnPasswordDisable Yes
NFOnPasswordDisableRecipients
NFNotifyOnVerificationErrors Yes
NFOnVerificationErrorsRecipients
NFNotifyOnPasswordUsed No
NFOnPasswordUsedRecipients
PasswordLength X value (Lets assume any value)
MinUpperCase (Lets assume any value)
MinLowerCase (Lets assume any value)
MinDigit (Lets assume any value)
MinSpecial (Lets assume any value)
PasswordForbiddenChars
OneTimePassword No
ExpirationPeriod 90
VFVerificationPeriod 7
PasswordLevelRequestTimeframe No
11-01-2024 08:34 AM
hey @sanjay sah
If the users are manually changing the passwords to stored accounts then these values are what matter:
PasswordLength X value (Lets assume any value)
MinUpperCase (Lets assume any value)
MinLowerCase (Lets assume any value)
MinDigit (Lets assume any value)
MinSpecial (Lets assume any value)
PasswordForbiddenChars
I would suggest you review the policy settings and ensure the passwords being set meet or exceed the set values.
-Matt
11-01-2024 08:35 AM
It meets the requirements. We validated.
11-01-2024 08:47 AM
@Matt Jennison What I am doubting is --- is there any default list of forbidden characters which are not supported by CyberArk by design?
11-01-2024 08:56 AM
there are some, depending on the type of account:
https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/plug-in-terminal-plugin-controller.htm?Highlight=forbidden%20characters#Forbiddencharactersandwords
-Matt
11-01-2024 09:03 AM
Yes, this document explains about TPC engine based, however I have been using cloud based AWS platform. So, TPC based is also relevant for Cloud "CyberArk.Extensions.AWS.dll" i.e. "CANetPluginInvoker.exe" plugin engine? Furthermore, there were no any character in password which is in forbidden list
11-01-2024 07:18 PM
Curious, have you tried both with the classic and the modern UI (v10) interface.
Any difference in messaging?
I've just about always started with a windows local to create an unmanaged platform.
Any reason you started with cloud?
11-01-2024 07:33 PM
Hi Jayne,
Yes, tried with both classic and modern interface. Whenever user tried to insert the password using modern interface, it showed/displayed green colors in all policies rules meaning that it meets password complexities. However, when clicking OK to finalize password storage. It threw errors as stating that password doesn’t meet password complexities.
Secondly, with classic interface it just threw above error as stated in description.
The reason behind I started with cloud because these credentials are related to cloud accounts and few are Keys, I have provided users permission to add accounts. While adding accounts, they can find out and differentiate what type of accounts should go “where?” so they won’t have confusion while onboarding different password object and easily find out platforms. I don’t have issue with platform which holds keys but only with the platform which is holding PCI regulated passwords.
I hope I could explain you clearly
11-01-2024 07:46 PM
They aren't really cloud accounts, though, are they, in the sense that you are not managing them in the cloud. You are basically using CyberArk as a password store only, and these are unmanaged accounts. (Unless there is something in that cloud platform that you are hoping to utilize on these accounts, they are truly just a basic password object).
What you might want to do is compare the two platforms : the one that works and the one that doesn't.
You also show that the account can be placed in any safe. That is a bit odd, but, I understand you taking it out whilst you are troubleshooting.
Curious. Have you created a safe with this platform and tried it yourself? Taking the user out of the picture might help you power through some tests.
Have you tried with the password they are trying?
Does it always not work, or sometimes work.
When you run an inventory report, is there anything special or odd about the account?
11-01-2024 07:54 PM
Actually those are Cloud Accounts but we are not managing using CA. I have proposed them but they ignored.
Have you tried with the password they are trying
Answer: I wanted but I was not permitted to see password, however I asked him all required questions based on policy. He was doing everything sharing the screen.
Does it always not work, or sometimes work
— Great Question, I have noticed sometime not working. What may be the reason?
When you run an inventory report, is there anything special or odd about the account?
— I haven’t done this. i will verify
11-01-2024 08:00 PM
Ok, so one possibility is that he is not getting the password that he thinks he is going into the account.
I've seen people do odd things without realizing.
Is the password something that they are setting? is there a possibility they are copying a trailing blank or a leading blank?
Set up a test safe with test account, and have them trial it a few times. Have them share the password with you.
11-01-2024 08:06 PM
I was also thinking same that he may be doing some mistakes bringing password from somewhere and not meeting complexities however CyberArk password console was displaying in green that password meets all requirements but while clicking on finalize it threw errors. Yes users bring passwords from somewhere, I tested on that space part too. It was not the issue.
I was thinking same to do test on test-safe with some random fake password however I asked him if he can generate password in CyberArk and push to his AWS cloud, and he agreed
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!

