Bug 32209 – Wrong UDM policy shown during object creation

Bug 32209 - Wrong UDM policy shown during object creation


Summary:	Wrong UDM policy shown during object creation

Status:	CLOSED DUPLICATE of bug 31916

Product:	UCS
Classification:	Unclassified
Component:	UMC - Policies
Version:	UCS 3.1
Hardware:	All Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.1-1-errata
Assigned To:	Alexander Kläser
QA Contact:	Florian Best

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-08-09 11:03 CEST by Philipp Hahn
Modified:	2013-08-29 07:23 CEST (History)
CC List:	2 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):	Usability
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 Philipp Hahn

2013-08-09 11:03:33 CEST

Ticket#: 2013061221001009 UCS Training video

Multiple OUs with multiple cn=users sub-containers with different policies for users.
If a new user is directly created in one of those sub-containers, the policy tab only shows the default policy.
The different policy is only applied when the object is created, which might fail when the sub-container has a more specific policy, e.g. the default password policy only required 8 characters, but the specific policy required 12 characters.

Comment 1 Philipp Hahn

2013-08-09 12:36:48 CEST

Strange, I can't reproduce it: Now the correct policy setting are shown, even during creation, but I know that it didn't work at the recording.
So there might be some strange pre-conditions, which are needed to show the bug.

Comment 2 Alexander Kläser

2013-08-22 18:28:49 CEST

Sounds much like a duplicate of Bug 31916.

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

Comment 3 Florian Best

2013-08-23 13:46:40 CEST

Yes, this is the same problem.

Comment 4 Stefan Gohmann

2013-08-29 07:23:16 CEST

OK, nothing to release.