fix: Enforce minimum range boundaries for security compliance (fixes #746)#753
Open
ymh1874 wants to merge 1 commit into
Open
fix: Enforce minimum range boundaries for security compliance (fixes #746)#753ymh1874 wants to merge 1 commit into
ymh1874 wants to merge 1 commit into
Conversation
openstack-experimental#746) This patch introduces runtime configuration validation rules ensuring that specific security compliance settings (like 'password_expires_days', 'disable_user_account_days_inactive', etc.) are explicitly greater than zero, mirroring openstack/keystone python implementation. The config crate has been updated to use the validator crate, and the ConfigManager now forcibly invokes validation on startup and file reloads. Signed-off-by: Yousef Hussein <ymh1874@gmail.com>
ymh1874
changed the title
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
1 participant
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.
This patch introduces runtime configuration validation rules ensuring that specific security compliance settings (like 'password_expires_days', 'disable_user_account_days_inactive', etc.) mirroring openstack/keystone python implementation.
The config crate has been updated to use the validator crate, and the ConfigManager now invokes validation on startup and file reloads.
Closes #746