Bug 25795 – Benutzerkonto für den Passwortdienst darf kein Leerzeichen enthalten

Bug 25795 - Benutzerkonto für den Passwortdienst darf kein Leerzeichen enthalten


Summary:	Benutzerkonto für den Passwortdienst darf kein Leerzeichen enthalten

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector - Windows password service
Version:	UCS 2.4
Hardware:	Other Linux

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

URL:
Keywords:

Duplicates:	16750 (view as bug list)
Depends on:
Blocks:	41137
	Show dependency tree / graph

Reported:	2012-01-10 09:55 CET by Janis Meybohm
Modified:	2016-04-26 09:35 CEST (History)
CC List:	4 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
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 Janis Meybohm

2012-01-10 09:55:25 CET

Berichtet an: http://forum.univention.de/viewtopic.php?f=48&t=1680

Wird ein Benutzerkonto mit einem Leerzeichen verwendet gibt es eine Fehlermeldung ("user_logon error: E_LOGON_WRONG_PASSWORD") in der ucs-ad-connector.log:

--
Waiting for a client to connect...
accept client connection...
Client Connected.
UserDN  = [ldap srv]
Command = [G]
User    = [4115]
user_logon error: E_LOGON_WRONG_PASSWORD
create packet 
 4  0  0  0  2  4  0  0 
send 8
Waiting for a client to connect...
---

Comment 1 Michel Smidt 2016-02-25 17:02:07 CET

Still an issue.

Comment 2 Michel Smidt 2016-02-25 17:02:34 CET

*** Bug 16750 has been marked as a duplicate of this bug. ***

Comment 3 Stefan Gohmann

2016-04-25 07:52:10 CEST

This issue has been filed against UCS 2.4.

UCS 2.4 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 use "Clone this bug".
In this case please provide detailed information on how this issue is affecting
you.