Bug 29943 – Misleading error message in univention-policy-result / Needs modification for authenticated LDAP access

Bug 29943 - Misleading error message in univention-policy-result / Needs modification for authenticated LDAP access


Summary:	Misleading error message in univention-policy-result / Needs modification for...

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	General
Version:	UCS 3.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Bugzilla Mailingliste
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-01-07 11:28 CET by Moritz Muehlenhoff
Modified:	2016-10-11 10:05 CEST (History)
CC List:	2 users (show)

See Also:	35182
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 Moritz Muehlenhoff

2013-01-07 11:28:47 CET

Executing univention-policy-result with an existing DN yields the following error message:

root@master:~# univention-policy-result uid=jmm3,cn=users,dc=foobar,dc=jmm
LDAP Error: No such object

univention-policy-result cannot search in the LDAP directory without the credentials of a user being passed. Only if an LDAP user and a password are being passed with -D and -w (or -W) the policy retrieval is working as expected.

This used to work prior to UCS 3.0, which switched to mandatory LDAP authentication by default.

univention-policy-result should print a proper error message if no credentials are passed. 

To enhance usability it should automatically use the machine account if started with the root user.

Comment 1 Nico Stöckigt

2015-11-26 15:41:45 CET

seems to be connected with bug 35182

Comment 2 Stefan Gohmann

2016-10-11 08:04:30 CEST

This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please reopen.

Comment 3 Florian Best

2016-10-11 10:05:46 CEST

Since we disallow anonymous access:

# univention-policy-result $(ucr get ldap/hostdn)
LDAP Error: Insufficient access