dogtagpki

#451 RFE: add mechanism to enforce quality of user's PINs in TPS
Closed: migrated by dmoluguw. Opened by nkinder.

Closed: migrated
Reopen Issue

There are no validation routines that can be used to validate the quality of PINs when they are created by the end user other than length constraints. There should be rules that limit repeating characters, define the character set (alpha, numeric, special character) and the number of each. Today you can enter 00000000 as a valid PIN.

Metadata Update from @nkinder:
- Issue assigned to vakwetu
- Issue set to the milestone: UNTRIAGED

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1022

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
Normal
enhancement
TPS
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.