Bug 40910 – LDAP-"operational attributes" als extended attribute verfügbar machen

Bug 40910 - LDAP-"operational attributes" als extended attribute verfügbar machen


Summary:	LDAP-"operational attributes" als extended attribute verfügbar machen

Status:	RESOLVED DUPLICATE of bug 20235

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

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

URL:
Keywords:

Depends on:	55670 20235
Blocks:	25907
	Show dependency tree / graph

Reported:	2016-03-16 20:19 CET by Kevin Dominik Korte
Modified:	2023-02-13 12:31 CET (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):
Max CVSS v3 score:

Attachments
Patch (444 bytes, patch) 2016-03-16 20:19 CET, Kevin Dominik Korte	Details \| Diff
View All 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 Kevin Dominik Korte

2016-03-16 20:19:35 CET

Created attachment 7540 [details]
Patch

+++ This bug was initially created as a clone of Bug #20235 +++

Ich habe gerade versucht "creatorsName" oder "modifyTimestamp" per Extended Attribute azuzeigen, die Felder sind aber leer. Es wäre sehr angenehm wenn das ginge.

Ich vermute dass dazu beim Suchen nach Objekten "+" in die Liste der Attribute im search aufgenommen werden muss; wenn vorher kein Attribute angegeben war müsste man ["*","+"] mitgeben.


Still exists with UCS 3.2 and requested by a customer.

Comment 1 Florian Best

2016-03-17 06:13:06 CET

Why did you clone this bug? The origin bug is still opened and contains a slightly different patch.

Comment 2 Kevin Dominik Korte

2016-03-17 14:50:48 CET

From my understanding, the issue penetrates to a different UCS Version.

Comment 3 Florian Best

2016-03-18 06:16:44 CET

(In reply to Kevin Dominik Korte from comment #2)
> From my understanding, the issue penetrates to a different UCS Version.
There is no target milestone set. I changed the version at the origin bug to UCS 3.2 and close this as duplicate.

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