Bug 37588 – Sytem users should be excluded from default user settings for apps

Bug 37588 - Sytem users should be excluded from default user settings for apps


Summary:	Sytem users should be excluded from default user settings for apps

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-01-22 15:12 CET by Nico Gulden
Modified:	2020-07-03 20:55 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Feature Request
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):	External feedback, Roadmap discussion (moved)
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 Nico Gulden

2015-01-22 15:12:42 CET

Feedback from the App Center Expert Talk at Univention Summit 2015. 

Some apps, like ownCloud, activate the default user setting, as soon as they are installed. Every new user is then automatically able to use the app. This mechanism should exclude system users.

Example: Running UCS in AD member mode with ownCloud installed, allows every user in AD to login to ownCloud. That's the expected behaviour. Installing Samba 4 creates some system users and they are allowed to login to ownCloud, as well. They should not be allowed to do so.

Comment 1 Dirk Wiesenthal

2017-04-07 11:34:50 CEST

Shouldn't this be handled by the App by using a more specific LDAP filter?

Comment 2 Ingo Steuwer

2020-07-03 20:55:16 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have 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" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.