-
Notifications
You must be signed in to change notification settings - Fork 259
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
test: authentication, adding generic password policy tests #7728
test: authentication, adding generic password policy tests #7728
Conversation
danlavu
commented
Nov 30, 2024
•
edited
Loading
edited
- depends on roles, adding default domain password policy management sssd-test-framework#139
- added generic password change tests
- removed generic password change tests in test_ldap and made them only ppolicy tests, since generic now covers ldap
- renamed test_ldap names.
- updated assertions, client.auth.ssh.password_with_output, now returns a different value because of the mentioned pull request
bfc5ed5
to
aea7f4e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of places missing ()'s I think.
aea7f4e
to
1242992
Compare
1242992
to
20248d2
Compare
Will post the test_authentication runs when they are done, but all the test are passing with SSSD/sssd-test-framework#139 |
bf3564c
to
a1a7718
Compare
This is ready for review. |
a1a7718
to
28554ea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly comment/wording changes suggested with a few questions mixed in. Looks like a good set of tests for password policy.
1da3edb
to
922826c
Compare
39c5577
to
adb13f2
Compare
* user is forced to changed password at login * user logins and issues a password change
* few scenarios have been removed * ppolicy tests have been made into ppolicy tests only, since normal ldap is covered by the generic provider now * renamed some of the test cases * removed su from a password change test * removed some test cases that are now covered by the new test cases
adb13f2
to
000121d
Compare
000121d
to
1a08a2a
Compare
I cancelled the CI run since they are going to fail. Here is the link to a successful run, the failure in Fedora 42 is not related. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly questions about docstring setup/steps wording.
:customerscenario: True | ||
""" | ||
old_password = "Secret123" | ||
invalid_password = "secret" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the variables match wording used in the docstrings (i.e. bad_password instead of invalid_password)?
3. Start SSSD | ||
:steps: | ||
1. Login as user | ||
2. Issue password change as user with password that does not meet complexity requirements |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought but if we're trying to simplify wording in docstrings, could we drop "as user with password" from this and the next step and have it still explain well enough what is happening?
LDAP modify. | ||
The 'test_authentication__change_password' test is a generic provider test that already | ||
covers LDAP. This test is an edited copy that only tests LDAP with the ppolicy overlay. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "covers" indented an extra space?
2. Configure the LDAP ACI to permit user password changes | ||
3. Set "ldap_pwmodify_mode" | ||
4. Start SSSD | ||
1. Create user 'user' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were we going to suggest dropping specifics like 'user' from the docstring setup and steps?
2. Configure the LDAP ACI to permit user password changes | ||
3. Set "ldap_pwmodify_mode" | ||
4. Start SSSD | ||
1. Create user 'user' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to state 'user' here or would removing that be in line with some of the simplification of steps/setup we've talked about?
4. Start SSSD | ||
:steps: | ||
1. Attempt to change the password but enter the incorrect password | ||
1. Login as user | ||
2. Issue password change as user with password that does not meet complexity requirements |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question as above about shortening steps by removing "as user with password".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussing with @danlavu , I'm approving this now since all of my latest questions/comments are related to docstring wording in some way. This can be addressed in a later effort.
F42 still fails |
@danlavu, please open explicit backport requests. |