restart Skype for Business client (to get the registry key effective).add AlwaysUseMSOAuthForAutoDiscover according this KB article.I’ve found a temporary workaround for this:
As result the client issues a SOAP Autodiscover request and the response contains all needed information The second request didn’t contains an empty “ Authorization: Bearer” header and therefore the response contains the X-SOAP-Enabled header. Which results in a POX request, which doesn’t contains the user setting Internal/ExternalPhotosURL Looking into the headers we can see that the first request contained an empty “ Authorization: Bearer” header, which caused that the server’s response hasn’t the X-SOAP-Enabled header. This headers controls whether the Skype for Business client issues a POX or a SOAP Autodiscover request. On the first view there seems to be no difference, but when you look closer you will see that in the second request the response contains an additional header X-SOAP-Enabled.
Now that I knew how it works in general, I started tracing and the tool for this is Fiddler (read my post for practical usage).įirst have a look into the Autodiscover requests GetUserSetting is only available as SOAP request. SOAP allows you to request single user settings. The main difference is that POX returns a complete configuration with basic information. Whereas when EWS is used it’s a SOAP request.Īs mentioned in the protocol details here, GetUserPhoto uses the Internal/ExternalPhotosURL from the Autodiscover response for GetUserSetting.Īutodiscover service supports 2 different services: Those are complete different ways as when you’re using REST the URL is like this: Server/ews/Exchange.asmx/s/GetUserPhoto?email=email address&size=size To retrieve the photo from a mailbox you could use two options: When the picture is uploaded to user’s mailbox, the picture is stored in the root of your mailbox in the item IPM.UserPhoto in different resolutions:
There are two ways to configure your profile picture:
0 kommentar(er)
