Bug 43725 – password and account expiry checks in shadowbind overlay cannot be disabled separately

Bug 43725 - password and account expiry checks in shadowbind overlay cannot be disabled separately


Summary:	password and account expiry checks in shadowbind overlay cannot be disabled s...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-06 12:04 CET by Felix Botner
Modified:	2019-01-03 07:19 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
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

2017-03-06 12:04:05 CET

(In reply to Sönke Schwardt-Krummrich from Bug #36215)
> Would be great if the checks for password expiration and account expiration 
> could be activated independently. I see UCS@school+CSP scenarios where account 
> expiration is desired but password expiration would lead to problems.

Comment 1 Stefan Gohmann

2017-04-18 08:00:48 CEST

The School Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the School Customer affected flag will be reset.

Comment 2 Stefan Gohmann

2019-01-03 07:19:19 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.