Office 365 version 16.26 (MAC OS) stop working with on-premise ADRMS (Right Management Services)

%3CLINGO-SUB%20id%3D%22lingo-sub-723233%22%20slang%3D%22en-US%22%3EOffice%20365%20version%2016.26%20(MAC%20OS)%20stop%20working%20with%20on-premise%20ADRMS%20(Right%20Management%20Services)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-723233%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%20did%20anyone%20face%20the%20same%20problem%20before%3F%20Could%20you%20please%20share%20some%20information%20about%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETL%3BDR%20-%20Office%20365%20on%20MAC%20stop%20working%20with%20our%20local%20ADRMS%20since%20latest%20update%20(16.26%2C%2016.27).%20All%20the%20old%20versions%20are%20fine%20(Office%20for%20MAC%202016%2C%20Office%20365%20version%20up%20to%2016.25)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20some%20more%20info%20regarding%20the%20problem%20we%E2%80%99re%20facing%3A%3C%2FP%3E%3COL%3E%3CLI%3EWe%20are%20using%20ADRMS%20on-premise%20with%20Mobile%20Extension%20and%20ADFS%3C%2FLI%3E%3CLI%3EWe%20have%20everything%20working%20properly%20in%20Office%20for%20Windows%2C%20the%20issue%20only%20applies%20for%20Office%20for%20Mac%20after%20the%20recent%20update%2C%2016.26%20and%2016.27%20are%20both%20affected%20based%20on%20our%20testing%3C%2FLI%3E%3CLI%3EFor%20the%20flow%20%26amp%3B%20screenshots%3A%3COL%3E%3CLI%3EThe%20problem%20is%20happening%20right%20when%20you%20try%20to%20open%20RMS-secured%20file%20during%20initial%20handshake%3C%2FLI%3E%3CLI%3EFirst%20you%20get%20the%20usual%20popup%20asking%20if%20you%20trust%20the%20server%20(our%20case%20is%20our%20local%20AD%20RMS)%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120811i7091C5586CDE8ABE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sodmacpopup.png%22%20title%3D%22sodmacpopup.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3EOnce%20you%20click%20%E2%80%98Continue%E2%80%99%2C%20it%20will%20get%20stuck%20at%20this%20%E2%80%98Authenticating%E2%80%A6%E2%80%99%20dialog%2C%20which%20will%20remain%20in-progress%20forever%20until%20you%20force%20close%20the%20app%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F120812iD2B5889CFCACBAEF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sodformacstuck.png%22%20title%3D%22sodformacstuck.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3ENotes%3A%3CUL%3E%3CLI%3E%3CSPAN%3EI%E2%80%99ve%20captured%20RMS%20logs%20from%20different%20versions%20of%20Excel%20on%20Mac%20apps%20when%20opening%20secured%20files%20(see%20attachments)%20%E2%80%93%20for%2016.26%20%26amp%3B%2016.27%20both%20the%20issue%20(Excel%2FWord%20getting%20stuck%20and%20unable%20to%20open%20the%20RMS-secured%20doc)%20persists%20and%20the%20logs%20are%20the%20pretty%20much%20the%20same%20for%20each%20attempt%3B%2016.25%2C%20however%2C%20is%20stable%20and%20properly%20opens%20RMS-secured%20files%20every%20time%20(you%20can%20see%20in%20logs%20that%20there%20are%20many%20more%20requests%20happening%20there%20for%20the%20license%20info%20%26amp%3B%20audit%20logging)%3C%2FSPAN%3E%3CUL%3E%3CLI%3EDeeper%20investigation%20of%20the%20logs%20%26amp%3B%20web%20traffic%20from%20Excel%2FWord%20apps%20shows%20that%2016.26%20is%20issuing%20%E2%80%98servicediscovery%E2%80%99%20API%20call%20and%20once%20it%20completes%20authorization%20round%2C%20then%20there%20are%20no%20more%20requests%20being%20issued%20from%20the%20client%3B%20whereas%2016.25%20continue%20sending%20requests%20to%20%E2%80%98enduserlicenses%E2%80%99%20and%20%E2%80%98clientlogs%E2%80%99%20APIs%20right%20after%20that%20%E2%80%98servicediscovery%E2%80%99%20call%20(note%3A%20the%20call%20returns%20the%20same%20response%20content%20for%20both%20versions%20of%20the%20app%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EThe%20problem%20happens%20with%20all%20of%20the%20files%2C%20it%20either%20works%20with%2016.25%20or%20doesn%E2%80%99t%20with%2016.26%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-723233%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EADRMS%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20for%20Mac%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

Hello all, did anyone face the same problem before? Could you please share some information about this?

 

TL;DR - Office 365 on MAC stop working with our local ADRMS since latest update (16.26, 16.27). All the old versions are fine (Office for MAC 2016, Office 365 version up to 16.25)

 

Here is some more info regarding the problem we’re facing:

  1. We are using ADRMS on-premise with Mobile Extension and ADFS
  2. We have everything working properly in Office for Windows, the issue only applies for Office for Mac after the recent update, 16.26 and 16.27 are both affected based on our testing
  3. For the flow & screenshots:
    1. The problem is happening right when you try to open RMS-secured file during initial handshake
    2. First you get the usual popup asking if you trust the server (our case is our local AD RMS) sodmacpopup.png
    3. Once you click ‘Continue’, it will get stuck at this ‘Authenticating…’ dialog, which will remain in-progress forever until you force close the app sodformacstuck.png
    4. Notes:
      • I’ve captured RMS logs from different versions of Excel on Mac apps when opening secured files (see attachments) – for 16.26 & 16.27 both the issue (Excel/Word getting stuck and unable to open the RMS-secured doc) persists and the logs are the pretty much the same for each attempt; 16.25, however, is stable and properly opens RMS-secured files every time (you can see in logs that there are many more requests happening there for the license info & audit logging)
        • Deeper investigation of the logs & web traffic from Excel/Word apps shows that 16.26 is issuing ‘servicediscovery’ API call and once it completes authorization round, then there are no more requests being issued from the client; whereas 16.25 continue sending requests to ‘enduserlicenses’ and ‘clientlogs’ APIs right after that ‘servicediscovery’ call (note: the call returns the same response content for both versions of the app
      • The problem happens with all of the files, it either works with 16.25 or doesn’t with 16.26
0 Replies