The SFB client now sends a SIP register to the Online Edge pool (' port='443) In Response Autodiscover will provide the Pool names (' port='443) where the client can send Register to Sign in The client then submits this webticket to Autodiscover

Webticket service now will grant a Webticket to the Client The Client then submits this token to Webticket Service The Client may receive a Password prompt and once the correct password is provided Org ID will issue a Token Now in order to authenticate the client reaches out to Ord ID and requests a Token The Client then sends a POST request to Webticket Service which requires the client to provide a Token from Org ID () The Client is then challenged and is provided the URL for Webticket service ( SFB Client then sends a Request to Autodiscover to discover its pool for sign in. The Client is then redirected to Autodiscover ( SFB Client then sends a unauthenticated GET request to SIP URI of the user - client Queries DNS for. My intention here is to explain what happens in the background when a SFB client signs in so that it helps engineers and customers troubleshooting issues related to Sign in and Authentication.īelow is a High level explanation on how the SFB online Client Sign in process works may not be standard terminology, I use them solely to make the understanding simpler.

Some of the terms I use to describe things like Modern Auth provider, O365 AD, Org ID etc. I have tried my best to ensure the information below is accurate. Pure Online (O365) environment, SFB user is homed Online, NO ADFS, MA (Modern Auth) is Disabled in O365 First published on TECHNET on Apr 09, 2018

Skype for business login