Bug 53835 – Contact creation adds numbers to generated cn

Bug 53835 - Contact creation adds numbers to generated cn


Summary:	Contact creation adds numbers to generated cn

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UMC - Users
Version:	UCS 5.0
Hardware:	All All

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-09-24 14:07 CEST by Jan Schampera
Modified:	2021-09-24 15:32 CEST (History)
CC List:	1 user (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 Jan Schampera 2021-09-24 14:07:13 CEST

While importing a CSV containing contacts using the UMC API (here: Python bindings, but also happens with cli) I noticed that the generated LDAP objects have a number to their generated cn appended.

So I have contact objects with cn: NAME LASTNAME 1

There is no obvious way to influence the generated cn.

I guess that this mechanism is there to avoid duplicates. But this could be done for the second (and more) generated objects, not right for the first one.

The problem here is (that's also where the issue raised) that some of my devices querying the contact lists show the cn attribute instead of a configurable attribute. This is just ugly.

Expecting either a hint for the cli/API to influence the generated cn attribute or a more intuitive mechanism against duplication (i.e. don't number all objects, number only the duplicates).

Comment 1 Florian Best

2021-09-24 15:32:54 CEST

(In reply to Jan Schampera from comment #0)
> While importing a CSV containing contacts using the UMC API (here: Python
> bindings, but also happens with cli) I noticed that the generated LDAP
> objects have a number to their generated cn appended.
> 
> So I have contact objects with cn: NAME LASTNAME 1
> 
> There is no obvious way to influence the generated cn.
> 
> I guess that this mechanism is there to avoid duplicates. 
Correct.

> But this could be
> done for the second (and more) generated objects, not right for the first
> one.
From reading the code, this should already be the case. hmm :-(

> The problem here is (that's also where the issue raised) that some of my
> devices querying the contact lists show the cn attribute instead of a
> configurable attribute. This is just ugly.
Yes, I would like to remove this completely or raise an error message instead when trying to create a duplicate entry.