Bug 45347 - [gapps] option to disable (not delete) gapps user, when ucs user is deleted
[gapps] option to disable (not delete) gapps user, when ucs user is deleted
Product: UCS
Classification: Unclassified
Component: Google Apps for Work
UCS 4.2
Other Linux
: P5 normal with 2 votes (vote)
: ---
Assigned To: Mail maintainers
Mail maintainers
Depends on:
  Show dependency treegraph
Reported: 2017-09-08 08:26 CEST by Daniel Tröder
Modified: 2020-07-03 20:50 CEST (History)
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?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017080121000378
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2017-09-08 08:26:22 CEST
The currently gapps listener code deletes a gapps user account, when the synced ucs account is deleted. Create an option (UCR variable) to change the behavior so that the gapps user is only deactivated.

Optional: check if the feature that the google admin console has - storing the users data into another account - is available through the API.

Forum: https://help.univention.com/t/experiences-google-apps-for-work-connector/6618/2
Comment 1 Tobias Birkefeld univentionstaff 2017-09-08 09:56:21 CEST
Also requested by customer Ticket#2017080121000378
Comment 2 Megachip 2018-04-09 15:33:04 CEST
It even deletes user, when someone removes the checkmark to gapps. In that case the user account is still fully functional in ucs.
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:50:58 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.