Bug 50541 - [o365] default ad connection not shown on user object
[o365] default ad connection not shown on user object
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Office 365
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Arvid Requate
Erik Damrose
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-11-25 17:05 CET by Erik Damrose
Modified: 2020-02-13 09:51 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2019-11-25 17:05:08 CET
When activating a user for Office365, the object is created in the Azure AD, but the connection is not shown on the user object. The user listener has to not only activate the user for the default connection, but modify the user object accordingly.
Comment 1 Erik Damrose univentionstaff 2019-11-27 17:45:42 CET
Arvid fixed it in 178988e203fbd38c9380d7e8e38368758143b0b5 with a wrong bug number (50460)
Comment 2 Erik Damrose univentionstaff 2019-11-27 17:46:18 CET
Verified: Just enabling a user will add the defaultADconnection to the object when the respective UCRv is set
Comment 3 Erik Damrose univentionstaff 2020-02-13 09:51:25 CET
Closed: Released with App Version 3.0 for UCS 4.4