Back to bug 1024959
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Martin Kosek | 2013-10-30 16:47:51 UTC | Doc Text | Cause: Identity Management server does not write the initial user password correctly to password history. Consequence: When a new Identity Management user is created and a password is generated for him, the first time that user changes the password, the value of the first password is disregarded when the password policy plugin checks the password history. This means that user can "change" the initial password to the same value as the previous one, with no regards to configured password history. Password history is applied correctly to all subsequent password changes. Workaround (if any): No known workaround. Result: N/A |
|
| Martin Kosek | 2013-10-30 16:48:48 UTC | Status | NEW | CLOSED |
| Resolution | --- | NEXTRELEASE | ||
| Doc Type | Bug Fix | Known Issue | ||
| Last Closed | 2013-10-30 12:48:48 UTC | |||
| Red Hat Bugzilla | 2013-10-30 16:48:48 UTC | Doc Type | Known Issue | Bug Fix |
| Eliska Slobodova | 2013-11-04 12:29:33 UTC | Doc Text | Cause: Identity Management server does not write the initial user password correctly to password history. Consequence: When a new Identity Management user is created and a password is generated for him, the first time that user changes the password, the value of the first password is disregarded when the password policy plugin checks the password history. This means that user can "change" the initial password to the same value as the previous one, with no regards to configured password history. Password history is applied correctly to all subsequent password changes. Workaround (if any): No known workaround. Result: N/A | The Identity Management server does not write the initial user password correctly to password history. As a consequence, when a new Identity Management user is created and a password is generated for him, the first time that user changes the password, the value of the first password is disregarded when the password policy plug-in checks the password history. This means that user can "change" the initial password to the same value as the previous one, with no regards to the configured password history. Password history is applied correctly to all subsequent password changes. |
| Doc Type | Bug Fix | Known Issue |
Back to bug 1024959