New Issue Yesterday (2016-04-13) with O365 Desktop Clients

[Thomas M. Wilson]

We just started seeing this yesterday as well.  We're not using Shibboleth for our O365 authentication, but we're seeing the same problem on our ADFS servers.  It is only happening to a small number of users.

We're on the phone with Microsoft right now about this problem in fact.


Tom Wilson
Systems Administrator IV
University of Wyoming
Division of Information Technology
Laramie, WY 82071
Thomas.Wilson at uwyo.edu
(307)766-2708



-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Christopher Bongaarts
Sent: Thursday, April 14, 2016 11:08 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: New Issue Yesterday (2016-04-13) with O365 Desktop Clients

On 4/14/2016 12:03 PM, Cantor, Scott wrote:
>> The difference I have found is the parameter on the path:  &popupui=1
> That's not a parameter, though. There's no query string. That's effectively adding to the path. If it were a parameter, it would be ignored.
>
>> Anyone else seeing this?
>> This seems like a problem with O365 applications, not something we could or
>> should fix in handler.xml.
> Short of a Java filter, I doubt you could.

Might be able to work around it by adding a "?" to the end of your SSO 
endpoint in the O365 config... (yuck)

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net