Bug 47517 – shadowLastChange handling in password.py

Bug 47517 - shadowLastChange handling in password.py


Summary:	shadowLastChange handling in password.py

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:	47518
	Show dependency tree / graph

Reported:	2018-08-09 10:10 CEST by Felix Botner
Modified:	2021-05-03 21:47 CEST (History)
CC List:	1 user (show)

See Also:	41574 45957
What kind of report is it?:	Development Internal
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

2018-08-09 10:10:25 CEST

related to Bug #45957

once Bug #45957 is fixed, we have to double check connector behavior, 

s4->ucs
 * shadowLastChange=0 if pwdLastSet=0 (pwdLastSet in AD means 
   changePasswordOnNextLogin, the same for shadowLastChange=0 for
   linux/shadow)
 * set shadowMax only if a pw policy exists
 * set krb5PasswordEnd to "now -1" if pwdLastSet==0 (this is Bug #47508)

ucs->s4
 * ?? check