Bug 45728 – Login at the UMC for users should be case sensitive

Bug 45728 - Login at the UMC for users should be case sensitive


Summary:	Login at the UMC for users should be case sensitive

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 4.1
Hardware:	Other Mac OS X 10.1

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-17 12:22 CET by Michel Smidt
Modified:	2019-01-03 07:24 CET (History)
CC List:	2 users (show)

See Also:	38826
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?:	1: Will affect a very 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.034
Enterprise Customer affected?:
School Customer affected?:	Yes
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 Michel Smidt 2017-11-17 12:22:42 CET

A lot of functions in the UMC seems to be case sensitive so that this is really an issue for customers. The customer reported several issues were a school create a user like "Testuser" and than logged in with "testuser" in the UMC which broke a lot of functionality.
I know that windows services are case insensitiv and guess for this reason the login at the UMC is similiar but I would prefer to force case sensitive login.

Comment 1 Florian Best

2017-11-17 12:29:31 CET

Can you be more concrete on what fails? We had issues in the past which we fixed:
after an login the username - as it is in LDAP - is send back to the frontend.

Maybe we should additionally use the normalized username in the backend: 
class Instance(Base):
 …
 self.username = normalized_username

Should be easy to fix.

Comment 2 Michel Smidt 2017-11-17 12:35:44 CET

(In reply to Florian Best from comment #1)
> Can you be more concrete on what fails? We had issues in the past which we
> fixed:
> after an login the username - as it is in LDAP - is send back to the
> frontend.
> 
> Maybe we should additionally use the normalized username in the backend: 
> class Instance(Base):
>  …
>  self.username = normalized_username
> 
> Should be easy to fix.

Sure, I will ask the customer. Problem here is that they are still on UCS 4.1-4. But I would guess that they can live with it if they know that it is fixed on  newer UCS versions.

Comment 3 Florian Best

2017-11-20 12:06:16 CET

In Bug #38826 a normalization of the username has been implemented in the backend.

Comment 4 Stefan Gohmann

2019-01-03 07:24:06 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

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