Bug 34846 – RDP (XRDP?) Session to Windows Terminal Server fails if password was changed

Bug 34846 - RDP (XRDP?) Session to Windows Terminal Server fails if password was changed


Summary:	RDP (XRDP?) Session to Windows Terminal Server fails if password was changed

Status:	CLOSED FIXED

Product:	Z_Univention Corporate Client (UCC)
Classification:	Unclassified
Component:	Documentation
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal
Target Milestone:	UCC 2.0
Assigned To:	Moritz Muehlenhoff
QA Contact:	Erik Damrose

URL:
Keywords:	interim-4

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-05-15 15:59 CEST by Moritz Muehlenhoff
Modified:	2014-06-12 09:19 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 Moritz Muehlenhoff

2014-05-15 15:59:55 CEST

Document in release notes

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

A user has to change the password on the next login. If that user logs on a UCC RDP Session lightdm asks for the new password, but the session to the windows server fails. 

lightdm saves the users password to allow /usr/share/xsessions/RDP to pass the password as a parameter to the rdpclient. But this password is saved before the password change.

Comment 1 Moritz Muehlenhoff

2014-06-02 09:13:19 CEST

Documented in the release notes.

Comment 2 Erik Damrose

2014-06-02 14:03:16 CEST

Documentation verified

Comment 3 Moritz Muehlenhoff

2014-06-12 09:19:55 CEST

UCC 2.0 has been released:
 http://docs.univention.de/release-notes-ucc-2.0.html

If this error occurs again, please use "Clone This Bug".