Project

General

Profile

Actions

Task #1573

closed

User attributes not allowed in passwords - check for the delimiters

Added by Alena Peterová about 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
High
Assignee:
Ondrej Husník
Category:
Password policy
Target version:
Start date:
03/25/2019
Due date:
% Done:

100%

Estimated time:
12.00 h
Owner:

Description

Please improve enhanced control for password policy - User attributes not allowed in password.

Now (9.5) we check if the whole username, first name, last name is a substring of the password. If the lastname is e.g. "Nováková-Dvořáková", then passwords containing only "novakova" are valid in IdM. But they are not valid in Active Directory, so when we provision passwords to AD, this creates problems.
On the other hand, if any part of the first name / last name is too short, it should be ignored when checking the password.

Suggested changes:
  • The username/firstName/lastName is parsed for delimiters: commas, periods, dashes or hyphens, underscores, spaces, pound signs, and tabs. If any of these delimiters are found, the username/firstName/lastName is split and all parsed sections (tokens) are confirmed not to be included in the password.
  • Tokens that are less than three characters in length are ignored, and substrings of the tokens are not checked.
  • For example, the name "Erin M. Hagens" is split into three tokens: "Erin," "M," and "Hagens." Because the second token is only one character long, it is ignored. Therefore, this user could not have a password that included either "erin" or "hagens" as a substring anywhere in the password.

(inspired by https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc786468(v=ws.10))

Actions

Also available in: Atom PDF