Sample configuration for password strength rules #1020
Merged
Conversation
This file contains 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
cliu123
reviewed
Feb 5, 2021
| # Password strength rules for password complexity. | ||
| # If you want to setup password strength rules for internal users, you can use below settings for it. | ||
| # Password validation rules can be configured through regex. In below regex example, user must need password with | ||
| # minimum 8 characters length and must include minimum one upercase, one kower case, one digit, and one special character. |
Codecov Report
@@ Coverage Diff @@
## master #1020 +/- ##
============================================
- Coverage 64.51% 64.51% -0.01%
+ Complexity 3167 3165 -2
============================================
Files 244 244
Lines 17034 17034
Branches 3022 3022
============================================
- Hits 10990 10989 -1
Misses 4507 4507
- Partials 1537 1538 +1
Continue to review full report at Codecov.
|
sujithvm
approved these changes
Feb 8, 2021
cliu123
approved these changes
Feb 8, 2021
chrousto
referenced
this pull request
in chrousto/security
Mar 6, 2021
* Sample setup for password strength configuration for internal user.
lbreinig
pushed a commit
to lbreinig/security
that referenced
this pull request
Dec 23, 2021
…1020) * Sample setup for password strength configuration for internal user.
wuychn
pushed a commit
to ochprince/security
that referenced
this pull request
Mar 16, 2023
…1020) * Sample setup for password strength configuration for internal user.
gaobinlong
pushed a commit
to gaobinlong/security
that referenced
this pull request
Aug 30, 2023
…earch-project#1020) Signed-off-by: Craig Perkins <cwperx@amazon.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
opendistro-for-elasticsearch/security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly
Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)
Documentation / Sample config
Github Issue # or road-map entry, if available:
Community Question: https://github.com/opendistro-for-elasticsearch/security/issues/1007
Sample yml configuration for password strength rules.
To provide sample configuration to users who want to setup password strength rules for internal users
N.A
N.A
N.A
N.A
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.