Bug 40924 – honor account deactivation in Office 365 App

Bug 40924 - honor account deactivation in Office 365 App


Summary:	honor account deactivation in Office 365 App

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Office 365
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-4-errata
Assigned To:	Daniel Tröder
QA Contact:	Erik Damrose

URL:
Keywords:

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

Reported:	2016-03-18 10:03 CET by Daniel Tröder
Modified:	2023-03-25 06:40 CET (History)
CC List:	4 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 Daniel Tröder

2016-03-18 10:03:19 CET

When a user account is deactivated, the listener should deactivate the corresponding Azure account too (set property accountEnabled=False).

Comment 1 Stefan Gohmann

2016-05-17 13:13:33 CEST

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

Comment 2 Daniel Tröder

2016-11-11 12:49:55 CET

r74336: [de]activate user depending on account expiry, deactivation and locking
r74341: listen for 'userPassword' to detect locked=posix
r74342: add ucs-test 92_office365/11_udm_deactive_lock_user for this bug and fix other ucs-tests

Package: univention-office365
Version: 0.2.12-6.43.201611111246
Branch: ucs_4.1-0
Scope: office365

Comment 3 Erik Damrose

2016-11-24 16:11:42 CET

OK: Deactivating user also blocks that user from using azure services
OK: Unblocking also works
Note: In my tests it took some time for this setting to be reflected in the AD interface
Verified