Bug 49416 - o365: change in manifest format breaks app setup
o365: change in manifest format breaks app setup
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Office 365
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Erik Damrose
Felix Botner
:
: 47964 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-05-06 10:17 CEST by Erik Damrose
Modified: 2019-07-11 10:01 CEST (History)
6 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.171
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019050921000801, 2019060421000363, 2019061121000475
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-05-06 10:17:49 CEST
The wizard to setup the office365 app guides the user to configure a manifest file in azure, which is required to setup the communication with the azure API.
It seems the manifest format changed in April 2019 [1]. The manifest our setup wizard creates is no longer compatible with the expected format in azure. Uploading the manifest to azure results in an error. New installations of the app can no longer be configured successfully, existing apps seem to continue to work.

[1] https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest
Comment 1 Christina Scheinig univentionstaff 2019-06-12 09:42:18 CEST
Happened again on a UCS 4.3-3
Comment 2 Erik Damrose univentionstaff 2019-06-17 17:47:52 CEST
2982781 backend changes in preparation for upcoming wizard adaption.
Comment 3 Erik Damrose univentionstaff 2019-06-20 17:39:29 CEST
8d1f5a33 Adapt wizard to Azure changes
* Updated manifest handling
* Added certificate down- and upload steps to wizard
* Updated wizard texts and screenshots (english)
Comment 4 Daniel Tröder univentionstaff 2019-06-26 11:24:54 CEST
(In reply to Erik Damrose from comment #3)
> 8d1f5a33 Adapt wizard to Azure changes
> * Updated manifest handling
> * Added certificate down- and upload steps to wizard
> * Updated wizard texts and screenshots (english)

OK: new screenshots for wizard
OK: new texts for wizard
OK: new certificate and manifest handling

MISSING: force user to connect through HTTPS to UMC
Comment 5 Daniel Tröder univentionstaff 2019-06-26 11:25:48 CEST
Switching assignee / QA for translation task.
Comment 6 Daniel Tröder univentionstaff 2019-06-26 13:01:01 CEST
Added german translations for texts and pictures:

[4.4 c2a2ba0] Bug #49416: add german translations

Please QA them and then reverse assignee / QA for the final two tasks:
* force HTTPS
* change link to point to the page for Windows Management Framework 5.1 (instead of 5.0, which is not downloadable anymore).
Comment 7 Erik Damrose univentionstaff 2019-07-02 14:56:06 CEST
Thanks, texts and screenshots are looking good.

In addition, i fixed:
[4.4 a0d5a62] Bug #49416: Add missing shadows to screenshots
[4.4 df91625] Bug #49416: Fix wizard: https + downloadlink
[4.4 c4a8ee5] Bug #49416: Fix wizard scroll behavior, item list numbering

Package: univention-office365
Version: 2.0.2-6A~4.4.0.201907021440
Branch: ucs_4.4-0
Scope: office365

Reassigning assignee / QA
Comment 8 Felix Botner univentionstaff 2019-07-04 15:51:00 CEST
OK - Apps work fine
Comment 9 Erik Damrose univentionstaff 2019-07-04 16:10:36 CEST
Released with UCS 4.4 app Microsoft Office 365 Connector Version 2.5
Comment 10 Erik Damrose univentionstaff 2019-07-11 10:01:35 CEST
*** Bug 47964 has been marked as a duplicate of this bug. ***