Bug 39218 – Provide UCR configurable LDAP write access to the users own LDAP object

Bug 39218 - Provide UCR configurable LDAP write access to the users own LDAP object


Summary:	Provide UCR configurable LDAP write access to the users own LDAP object

Status:	RESOLVED WONTFIX

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

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-08-19 10:31 CEST by Michael Grandjean
Modified:	2019-01-03 07:16 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?:	Yes
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 Michael Grandjean

2015-08-19 10:31:32 CEST

It should be possible to define a list of LDAP attributes via UCR, to which users should have write access (should affect only their own LDAP user object). 
This way, users would be enabled to modify certain attributes themself, e.g. contact information.

There is already "ldap/acl/user/password/change" that does basically what we want, but is limited to the password LDAP attributes.

Additionally we would need some documentation (wiki, sdb ...) on how to use extended attributes to display those attributes in the udm-self module.

Comment 1 Michael Grandjean

2015-08-28 14:07:22 CEST

Customer implementation via 2015081021000337

Comment 2 Michael Grandjean

2015-10-07 22:42:03 CEST

Also requested via 2015100721000375

Comment 3 Florian Best

2017-06-16 19:12:56 CEST

Still valid request?

Comment 4 Florian Best

2017-06-28 14:52:18 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 5 Stefan Gohmann

2019-01-03 07:16:16 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 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.