Bug 36318 – Remove posix lock if password is changed ?

Bug 36318 - Remove posix lock if password is changed ?


Summary:	Remove posix lock if password is changed ?

Status:	CLOSED DUPLICATE of bug 36215

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-2-errata
Assigned To:	Stefan Gohmann
QA Contact:	Felix Botner

URL:
Keywords:

Depends on:
Blocks:	36215
	Show dependency tree / graph

Reported:	2014-10-27 18:14 CET by Felix Botner
Modified:	2015-08-05 13:23 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2014-10-27 18:14:06 CET

For Bug #36215 we disable the posix account if the password is expired. In an NON-samba4 environment the posix lock is not removed during the password change of the user and the posix account is still locked (ldap bind is not possible).

Maybe we need to enable posix during password change if the password was expired or ./lock_expired_passwords from Bug #36215 has to set an additional flag "posixLockedBecausePasswordExpired" so we know we have to remove the posix lock during password change.

Comment 1 Janek Walkenhorst

2015-03-31 12:07:48 CEST

There have been no changes yet in Bug #36215.

Additionally it is questionable if always removing account locks on password change is a good policy.

Maybe resetting the flag should be part of the workaround implemented by Bug #36215.

Comment 2 Stefan Gohmann

2015-06-28 15:20:19 CEST

I think it should not be changed anything until Bug #36215 has been fixed.

*** This bug has been marked as a duplicate of bug 36215 ***