Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enforced password history allows passwords still in history #163

Closed
wwwysocki opened this issue Mar 24, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@wwwysocki
Copy link
Contributor

commented Mar 24, 2016

Repro:

  1. Enforce the password history with Composite.C1Console.Security.Plugins.PasswordPolicy/@passwordHistoryLength set to "3", which means (3 old password + 1 current password) (docs)
  2. Have the password for the C1 Console user expired.
  3. Use a new password 1 ('aaaaaa').
  4. Step 2 + Use a new password 2 ('bbbbbb').
  5. Step 2 + Use a new password 3 ('cccccc').
  6. Step 2 + Use a new password 4 ('dddddd'). (At this point, the last 4 passwords are 3 old ones 'aaaaaa', 'bbbbbb', 'cccccc' and the current one 'dddddd')
  7. Step 2 + Use the old password 1 ('aaaaaa').

Expected: The old password 1 ('aaaaaa') not accepted.
Actual: The old password (one of the three) accepted.

@mawtex

This comment has been minimized.

Copy link
Member

commented Mar 29, 2016

Vitaly, did you restart the C1 site after step 1?
(changes to Composite.config always require a site restart to be picked up)

@wwwysocki

This comment has been minimized.

Copy link
Contributor Author

commented Mar 31, 2016

Vitaly, did you restart the C1 site after step 1?

I have an impression that I did. But I just retested it, also restarting it every time after Step 2 - and the issue is gone (20160331.1).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.