Added Password Hardening tests cases - #1
Open
davidpil2002 wants to merge 10 commits into
Open
Conversation
…ead try exp, use show_and_parse build-in function instead coding a new one
davidpil2002
changed the title
… & rm init configuration in fixture
davidpil2002
force-pushed
the
passw_hardening
branch
from
April 7, 2022 12:14
6f1452f to
c0d0e5d
Compare
davidpil2002
force-pushed
the
passw_hardening
branch
2 times, most recently
from
May 1, 2022 12:04
f016452 to
66d3262
Compare
davidpil2002
force-pushed
the
passw_hardening
branch
from
May 1, 2022 12:36
66d3262 to
f0c999f
Compare
…ng explicity the feature disable Change-Id: Iea5b589290a7900b0585286ff3ef336f612e1b27
… loop when calling fixtures Change-Id: I43cf89ad498405521723e7fb164ef46929095b6b
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Added Password Hardening Tests according to HLD Test Plan
Context: By enabling the new Password Hardening feature and configured policies, the user will be enforce to use "strong" passwords according to the policies configured.
The new tests cases will cover all the possible password policies with good and bad cases, including:
Note
After creating a new policy is necessary to set a new password for a user to verify that the policy matches the configured.
The set configuration should be validated using the show command.
Type of change
Back port request
Approach
What is the motivation for this PR?
Add new tests cases for testing the feature Password Hardening.
How did you do it?
There are 10 test scenarios each one of them config different policies and test the case with good(strong) passwords and bad(weak) passwords expecting results according to the configuration and the flow.
The configuration is done by using sonic-cli, sending different "config" commands.
In addition, the test is testing that the configuration in PAM files in the system change according to the expected.
The expected files were saved in the directory "sample".
How did you verify/test it?
New tests cases passed
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
any
Documentation
Link of HLD including feature design and Test plan:
https://github.com/Azure/SONiC/blob/master/doc/passw_hardening/hld_password_hardening.md