An error occurred fetching the project authors.
- 06 Apr, 2020 2 commits
-
-
Jérome Perrin authored
Credential Recovery are supposed to be related to persons, not logins. Extend the tests to make sure that after the credential recovery is accepted a reset password email is sent and fix authentication_policy scripts to create a Credential Recovery related to the person.
-
Jérome Perrin authored
This may hide problems with code still expecting that person's reference is same as login. I did not find such problematic code, but I thought that it would be better anyway.
-
- 20 Jan, 2020 1 commit
-
-
Vincent Pelletier authored
__ac_name & __ac_password are only useful to get a cookie, so only use them when the test is actually expecting a cookie.
-
- 15 Nov, 2019 1 commit
-
-
Jérome Perrin authored
When we use preference.edit(preferred_something=something_else) the cache was cleared, because there is an interaction on _edit, but when we do preference.setPreferredSomething(something_else) cache was not cleared. This still have a problem cache is cleared too much but at least it eliminates this incorrect behavior. Update tests at the same time: - testEditorField,testAuthenticationPolicy: no need to clear cache, it's now done automatically. - testUpgrader: the workflow chain of preference changed. This test is asserting the actual workflow chain, so we have to update the test everytime workflow chain is modified.
-
- 16 Sep, 2019 1 commit
-
-
Romain Courteaud authored
See nexedi/erp5@28774376
-
- 19 Jan, 2017 4 commits
-
-
Jérome Perrin authored
Login_isPasswordValid is no longer used.
-
Jérome Perrin authored
When reseting password through portal_password, we should check new password comply with policy. Because user is not logged in at this stage, we expose a new method `PasswordTool.analyzePassword` that checks the password is valid for this reset key.
-
Jérome Perrin authored
-
Jérome Perrin authored
This is a change in the API, previously only "messages id" were returned. To make it easier to reuse analyzePassword in other contexts, we now return the message directly.
-
- 10 Jan, 2017 2 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
Tests should not depend on the state left by the previous test run. This was achieved by: * use a different preference in each method to reset the state of preferences configuration. * clear cache after setting preferences, so that the new preference setting is used * change password after setting the max preferred password lifetime duration, otherwise password event are not created and password is not detected as expired. * rename test methods not to include number, we should not force test ordering, since we want tests to be independant. * Also add one case of password actually expired
-
- 23 Dec, 2016 2 commits
-
-
Kazuhiko Shiozaki authored
-
Vincent Pelletier authored
-
- 10 Mar, 2015 1 commit
-
-
Gabriel Monnerat authored
-
- 16 Oct, 2014 1 commit
-
-
Julien Muchembled authored
-
- 04 Sep, 2014 1 commit
-
-
Gabriel Monnerat authored
-
- 12 Sep, 2013 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 15 May, 2012 1 commit
-
-
Julien Muchembled authored
This is a followup to commit 8995b645 ("always start transactions with begin() and make tic() commit automatically"): there is now no need to use self.stepTic() instead of self.tic()
-
- 11 May, 2012 1 commit
-
-
Julien Muchembled authored
-
- 03 May, 2012 1 commit
-
-
Sebastien Robin authored
-
- 16 Mar, 2012 1 commit
-
-
Ivan Tyagov authored
-
- 09 Sep, 2011 1 commit
-
-
Ivan Tyagov authored
-
- 15 Aug, 2011 1 commit
-
-
Ivan Tyagov authored
API. Adjust test accordingly.
-
- 28 Jul, 2011 1 commit
-
-
Ivan Tyagov authored
-
- 27 Jul, 2011 1 commit
-
-
Ivan Tyagov authored
Allow low level password validity checks (if isAuthenticationPolicyEnabled only). Adjust tests to handle better password history.
-
- 25 Jul, 2011 1 commit
-
-
Ivan Tyagov authored
Adjust test accordingly.
-
- 21 Jul, 2011 1 commit
-
-
Ivan Tyagov authored
saved. Add comment.
-
- 18 Jul, 2011 2 commits
-
-
Ivan Tyagov authored
-
Ivan Tyagov authored
-