Password Policy and Password Generator
Hey guys,
we are currently at a little hiccup at the "migration" into DVLS, we still have some passwords with 16 Characters that need to be accepted, but in future we want to enforce Users to use atleast 20.
So my idea would be:
Password Policy allows 16
Password Generator always generates 20
but i feel like thats not doable since the policy "password length" instantly binds the generator to its length.
Is this correct? If so, any other ideas?
All Comments (1)
One option could be to use multiple password policies and apply them at the vault level.
For example, if all existing 16-character passwords are stored in the same vault, that vault could be assigned a policy allowing 16 characters, while other vaults use a policy enforcing a 20-character minimum for new or updated credentials.
This allows existing entries to remain valid while enforcing the stronger requirement going forward, depending on how your vault structure is organized.
Kind regards,
Kelly