Bug 36801 – Add syntax check for home drive and home share

Bug 36801 - Add syntax check for home drive and home share


Summary:	Add syntax check for home drive and home share

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UMC - Users
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

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

Reported:	2014-11-18 12:05 CET by Arvid Requate
Modified:	2020-06-22 11:11 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
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 Arvid Requate

2014-11-18 12:05:01 CET

During the producttests I just had a case, where I accedentally flipped the fields for home drive and home share ("Laufwerk für das Windows-Heimatverzeichnis" vs "Windows-Heimatverzeichnis") and nothing worked.. I would be great to have a simple syntax check here, at least for one of them.

Comment 1 Florian Best

2018-01-31 15:23:40 CET

(In reply to Philipp Hahn from Bug #32171 comment #0)
> It only seems to work if the drive letter contains the trailing colon, that
> is
> "H" does not work
> "H:" does work
> 
> management/univention-directory-manager-modules/modules/univention/admin/
> handlers/users/user.py
>         'homedrive': univention.admin.property(
>                         syntax=univention.admin.syntax.string,

Comment 2 Florian Best

2018-01-31 15:23:47 CET

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