Bug 40925 – honor account deactivation in Google Apps for Work App

Bug 40925 - honor account deactivation in Google Apps for Work App


Summary:	honor account deactivation in Google Apps for Work App

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	Google Apps for Work
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:	37949
Blocks:
	Show dependency tree / graph

Reported:	2016-03-18 10:09 CET by Daniel Tröder
Modified:	2019-02-04 11:21 CET (History)
CC List:	3 users (show)

See Also:	44945
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?:	4: A User would return the product
User Pain:	0.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	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 Daniel Tröder

2016-03-18 10:09:55 CET

When a user account is deactivated, the listener should deactivate the
corresponding Google account too (set properties {suspended=True, suspensionReason=ADMIN}).

Comment 1 Daniel Tröder

2016-09-30 11:02:00 CEST

For google apps for work account this is a big problem, because customers pay per activated user account!

Comment 2 Stefan Gohmann

2019-01-03 07:18:22 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.

Comment 3 Daniel Tröder

2019-01-03 12:00:52 CET

Still important to fix.