Home
%3CLINGO-SUB%20id%3D%22lingo-sub-621263%22%20slang%3D%22en-US%22%3ESFB%20online%20Client%20Sign%20in%20and%20Authentication%20Deep%20Dive%20%3BPart%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-621263%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Apr%2009%2C%202018%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Scenario%3A%20%3C%2FSTRONG%3E%20Pure%20Online%20(O365)%20environment%2C%20SFB%20user%20is%20homed%20Online%2C%20ADFS%20is%20Configured%2C%20MA%20(Modern%20Auth)%20is%20Disabled%20in%20O365%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20%3CSPAN%20style%3D%22color%3A%20%23ff0000%22%3E%20NOTE%3A%20%3C%2FSPAN%3E%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20I%20have%20tried%20my%20best%20to%20ensure%20the%20information%20below%20is%20accurate.%20Some%20of%20the%20terms%20I%20use%20to%20describe%20things%20like%20Modern%20Auth%20provider%2C%20O365%20AD%2C%20Org%20ID%20etc.%20may%20not%20be%20standard%20terminology%2C%20I%20use%20them%20solely%20to%20make%20the%20understanding%20simpler.%20My%20intention%20here%20is%20to%20explain%20what%20happens%20in%20the%20background%20when%20a%20SFB%20client%20signs%20in%20so%20that%20it%20helps%20engineers%20and%20customers%20troubleshooting%20issues%20related%20to%20Sign%20in%20and%20Authentication.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EHow%20Does%20it%20Work%3F%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Below%20is%20a%20High%20level%20explanation%20on%20how%20the%20SFB%20online%20Client%20Sign%20in%20process%20works%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20alt%3D%22clip_image001%5B4%5D%22%20border%3D%220%22%20height%3D%22368%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115314i5207CF7E7C505B00%22%20title%3D%22clip_image001%5B4%5D%22%20width%3D%22591%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20SIP%20URI%20of%20the%20user%20-%20%3CA%3E%20NJ%40JohnsonDataSystems.com%3C%2FA%3E%20%3CBR%20%2F%3E%3COL%3E%3CBR%20%2F%3E%3CLI%3ESFB%20client%20Queries%20DNS%20for%20Lyncdiscover.domain.com.%20This%20should%20point%20to%20Webdir.online.lync.com%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ESFB%20Client%20then%20sends%20a%20unauthenticated%20GET%20request%20to%20Lyncdiscover.domain.com%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20is%20then%20redirected%20to%20Autodiscover%20%3CA%20href%3D%22https%3A%2F%2Fwebdir2a.online.lync.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Djohnsondatasystems.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fwebdir2a.online.lync.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Djohnsondatasystems.com%3C%2FA%3E%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ESFB%20Client%20then%20sends%20a%20Request%20to%20Autodiscover%20to%20discover%20its%20pool%20for%20sign%20in.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20is%20then%20challenged%20and%20is%20provided%20the%20URL%20for%20Webticket%20service%20(%20%3CA%20href%3D%22https%3A%2F%2Fwebdir2a.online.lync.com%2FWebTicket%2FWebTicketService.svc%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fwebdir2a.online.lync.com%2FWebTicket%2FWebTicketService.svc%20%3C%2FA%3E%20)%20where%20it%20can%20request%20a%20Webticket%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20then%20sends%20a%20POST%20request%20to%20Webticket%20Service%20which%20requires%20the%20client%20to%20provide%20a%20Token%20from%20Org%20ID%20(login.microsoftonline.com)%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ENow%20in%20order%20to%20authenticate%20the%20client%20reaches%20out%20to%20Ord%20ID%20and%20requests%20a%20Token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ESince%20the%20tenant%20is%20enabled%20for%20ADFS%20the%20client%20is%20redirected%20to%20the%20ON%20Premise%20ADFS%20server%20%3CA%20href%3D%22https%3A%2F%2Fsts.cloudsfb.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fsts.cloudsfb.com%3C%2FA%3E%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ESFB%20client%20will%20then%20send%20a%20request%20to%20ADFS%20server%20and%20request%20a%20token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20may%20receive%20a%20Password%20prompt%20(or%20previously%20saved%20password%20from%20credential%20manager%20is%20passed)%20and%20once%20the%20correct%20password%20is%20provided%2C%20ADFS%20will%20issue%20a%20Token%20to%20the%20client%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20then%20submits%20this%20token%20to%20Org%20ID%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EORG%20ID%20will%20now%20issue%20its%20own%20Token%20to%20the%20client%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20then%20submits%20this%20token%20that%20it%20received%20from%20ORG%20ID%20to%20Webticket%20Service%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EWebticket%20service%20now%20will%20grant%20a%20Webticket%20to%20the%20Client%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20then%20submits%20this%20webticket%20to%20Autodiscover%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EIn%20Response%20Autodiscover%20will%20provide%20the%20Pool%20names%20(sipfed2a.online.lync.com%22%20port%3D%22443)%20where%20the%20client%20can%20send%20Register%20to%20Sign%20in%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20SFB%20client%20now%20sends%20a%20SIP%20register%20to%20the%20Online%20Edge%20pool%20(sipfed2a.online.lync.com%22%20port%3D%22443)%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EIt%20is%20then%20challenged%20for%20authentication%20again%2C%20here%20the%20ONLY%20supported%20method%20of%20authentication%20is%20TLS-DSK%2C%20The%20client%20is%20provided%20a%20Cert%20provisioning%20URL%20(%20%3CA%20href%3D%22https%3A%2F%2Fwebdir2a.online.lync.com%3A443%2FCertProv%2FCertProvisioningService.svc%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fwebdir2a.online.lync.com%3A443%2FCertProv%2FCertProvisioningService.svc%20%3C%2FA%3E%20)%20in%20the%20401%20unauthenticated%20response%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20SFB%20client%20then%20sends%20a%20request%20to%20Certprov%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EHere%20again%20the%20Client%20is%20challenged%20for%20authentication%20and%20is%20redirected%20to%20webticket%20service%20to%20get%20Webticket%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20had%20already%20Obtained%20a%20webticket%20in%20step%2014%20above%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20will%20submit%20the%20same%20webticket%20obtained%20in%20step%2014%20to%20the%20Cert%20provisioning%20service%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20Client%20then%20receives%20a%20certificate%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20SFB%20client%20can%20now%20send%20a%20Register%20again%20and%20use%20the%20certificate%20it%20downloaded%20for%20authentication%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FOL%3E%3CBR%20%2F%3E%20Below%20is%20a%20graphical%20representation%20of%20the%20SFB%20online%20Client%20Sign%20in%20process%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20alt%3D%22clip_image002%5B4%5D%22%20border%3D%220%22%20height%3D%221128%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115315iA663FEC16221A34B%22%20title%3D%22clip_image002%5B4%5D%22%20width%3D%22968%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Detailed%20Explanation%20of%20SFB%20online%20Client%20Sign%20in%20process%20with%20LOG%20Snippets%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20SIP%20URI%20of%20the%20user%20-%20%3CA%3E%20NJ%40JohnsonDataSystems.com%20%3C%2FA%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20When%20a%20SFB%20client%20wants%20to%20Sign%20in%2C%20It%20needs%20to%20know%20where%20it%20can%20send%20its%20request%20to%20be%20able%20to%20Sign%20in.%20Whenever%20a%20user%20enters%20his%20SIP%20URI%20to%20sign%20in%20the%20SFB%20client%20forms%20an%20autodiscover%20URL%20using%20the%20domain%20name%20that%20it%20extracts%20from%20the%20users%20SIP%20URI%20to%20start%20the%20discovery%20process%20and%20then%20it%20sends%20an%20Unauthenticated%20Get%20request%20to%20the%20URL%2C%20lyncdiscover.domain.com.%20The%20response%20code%20for%20this%20request%20will%20be%20'200%20ok'%20and%20in%20the%20response%20we%20should%20receive%20the%20external%20webservices%20URL%20for%20autodiscover.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20You%20can%20see%20the%20request%20and%20Response%20below%20The%20SFB%20Client%20learns%20that%20it%20needs%20to%20Contact%20%3CA%20href%3D%22https%3A%2F%2Fwebdir2a.online.lync.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebdir2a.online.lync.com%2F%3C%2FA%3E%20It%20then%20tries%20to%20Do%20a%20TCP%20handshake%20with%20webdir2a.online.lync.com%2C%20Followed%20by%20a%20TLS%20handshake.%20(I%20haven't%20included%20the%20TCP%20and%20TLS%20handshake%20screen%20shots%20here%2C%20you%20can%20see%20those%20if%20you%20collect%20a%20Network%20trace%20while%20signing%20in)%20The%20client%20then%20sends%20a%20request%20to%20the%20Autodiscover%20URL%20for%20its%20own%20domain%20(in%20my%20case%20%40%20JohnsonDataSystems.com%20)%20and%20in%20Response%20it%20receives%20the%20Autodiscover%20URL's%20specific%20to%20the%20users%20Tenant.%20You%20can%20see%20the%20request%20and%20Response%20below%20The%20client%20then%20sends%20a%20request%20to%20the%20user%20URL.%20We%20are%20here%20trying%20to%20discover%20a%20specific%20users%20home%20pool%2C%20hence%20the%20request%20will%20go%20to%20the%20%E2%80%9CUser%E2%80%9D%20URL.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20In%20the%20response%2C%20the%20Client%20receives%20a%20Web%20ticket%20URL%2C%20which%20provides%20the%20location%20of%20the%20WebTicketService.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20You%20can%20see%20the%20request%20and%20Response%20below%20The%20Client%20then%20needs%20to%20send%20a%20Request%20to%20the%20Web%20ticket%20service%20URL%20in%20order%20to%20obtain%20a%20Web%20ticket.%20The%20client%20will%20send%20this%20request%20in%20a%20POST%20message%20to%20the%20web%20ticket%20Service%20and%20in%20response%20it%20receives%20the%20actual%20individual%20Web%20ticket%20service%20URL's%20The%20Client%20has%20to%20submit%20a%20Request%20to%20this%20web%20ticket%20URL%20now%20in%20order%20to%20obtain%20a%20web%20ticket.%20But%20if%20it%20does%20that%20then%20it%20will%20need%20to%20authenticate%20first%2C%20unless%20the%20Client%20authenticates%20itself%20it%20will%20not%20be%20issued%20a%20web%20ticket.%20Since%20this%20user%20is%20Homed%20in%20SFB%20online%20the%20Client%20needs%20to%20reach%20out%20to%20O35%20AD%20(Org%20ID)%20to%20get%20authenticated%20first%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20SO%20right%20now%20the%20Client%20has%20to%20First%20reach%20out%20to%20Org%20ID%20in%20order%20to%20authenticate%20and%20Get%20a%20Token.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20process%20of%20reaching%20out%20to%20Org%20ID%20is%20initiated%20with%20the%20help%20of%20Microsoft%20Online%20Sign%20in%20Assistant%20(also%20known%20as%20IDCRL)%20that%20is%20installed%20on%20the%20Computer.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20You%20may%20not%20always%20see%20this%20in%20the%20fiddler%20trace%2C%20this%20attempt%20to%20get%20Token%20from%20AD%20is%20called%20Org%20ID%20auth%20and%20is%20captured%20in%20IDCRL%20logs%20on%20the%20client%20PC%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20Client%20will%20try%20to%20reach%20Org%20ID%20(O365%20AD)%20to%20get%20a%20token%2C%20but%20since%20the%20Tenant%20is%20Enabled%20for%20ADFS%20the%20O365%20AD%20(org%20ID)%20will%20redirect%20the%20client%20to%20the%20ADFS%20Server%20URL%20and%20the%20client%20will%20have%20to%20request%20a%20Token%20from%20ADFS%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20way%20this%20works%20is%20%3CBR%20%2F%3E%3COL%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20first%20tries%20to%20reach%20Org%20ID%20(O365%20AD)%20to%20request%20a%20Token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EHere%20it%20learns%20that%20the%20tenant%20is%20enabled%20for%20ADFS%20so%20it%20has%20to%20now%20go%20to%20the%20ADFS%20URL%20first%20and%20ask%20for%20a%20token%20from%20ADFS%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20reaches%20out%20to%20ADFS%20and%20requests%20a%20Token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EADFS%20will%20challenge%20for%20authentication%20which%20will%20cause%20a%20Password%20prompt%20to%20appear%2C%20or%20the%20user%20credential%20stored%20in%20the%20credential%20manager%20will%20be%20passed%20to%20ADFS%20in%20which%20case%20the%20user%20will%20not%20be%20prompted%20for%20password%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EOnce%20the%20password%20is%20provided%20ADFS%20will%20provide%20the%20client%20a%20Token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20will%20then%20submit%20this%20token%20back%20to%20Org%20ID%20(O365%20AD)%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EOrg%20ID%20will%20in%20turn%20provide%20the%20client%20the%20Org%20ID%20token%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FOL%3E%3CBR%20%2F%3E%20You%20can%20view%20all%20the%20above%20if%20you%20open%20the%20IDCRL%20log%20(MSOTrace%20folder)%20in%20the%20IDCRL%20parser%2C%20A%20successful%20token%20retrieval%20from%20ADFS%20and%20Org%20ID%20should%20look%20like%20below%20in%20the%20Parser%20(A%20more%20detailed%20explanation%20can%20be%20found%20in%20the%20bottom%20of%20this%20document%20if%20needed%20for%20reference)%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20alt%3D%22clip_image007%5B3%5D%22%20border%3D%220%22%20height%3D%22291%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115320iE8F71EE9A32C569E%22%20title%3D%22clip_image007%5B3%5D%22%20width%3D%221190%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Once%20the%20Client%20receives%20a%20Token%20from%20O365%20AD%20(Org%20ID)%20it%20then%20submits%20this%20token%20to%20the%20Web%20Ticket%20Service%20%3CA%20href%3D%22https%3A%2F%2Fwebdir2a.online.lync.com%2FWebTicket%2FWebTicketAdvancedService.svc%2FWsFed_bearer%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fwebdir2a.online.lync.com%2FWebTicket%2FWebTicketAdvancedService.svc%2FWsFed_bearer%20%3C%2FA%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20In%20Response%20the%20Web%20Ticket%20Service%20will%20now%20Issue%20the%20Client%20a%20Web%20Ticket.%20You%20can%20see%20this%20in%20the%20Trace%20below%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20alt%3D%22clip_image008%5B3%5D%22%20border%3D%220%22%20height%3D%22699%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115321i016DA28F96D6FBD1%22%20title%3D%22clip_image008%5B3%5D%22%20width%3D%221213%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20Client%20will%20Then%20Submit%20this%20web%20ticket%20back%20to%20the%20AutoDiscover%20User%20URL%20-%20%3CA%20href%3D%22https%3A%2F%2Fwebdir2a.online.lync.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Djohnsondatasystems.com%26amp%3Bsipuri%3Dnj%40johnsondatasystems.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fwebdir2a.online.lync.com%2FAutodiscover%2FAutodiscoverService.svc%2Froot%2Fuser%3ForiginalDomain%3Djohnsondatasystems.com%26amp%3Bsipuri%3Dnj%40johnsondatasystems.com%20%3C%2FA%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20In%20response%20it%20will%20now%20receive%20the%20Internal%20and%20External%20addresses%20of%20the%20Pool%20names%20where%20the%20user%20is%20Homed.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20You%20can%20see%20this%20in%20the%20trace%20below%20Once%20the%20Client%20receives%20the%20pool%20names%20it%20will%20then%20Send%20a%20SIP%20REGISTER%20message%20to%20the%20SFB%20pool%20in%20order%20to%20sign%20in.%20.%20You%20can%20see%20that%20in%20the%20Client%20UCCAPI%20log%20file.%20This%20is%20shown%20in%20the%20snippet%20below%20In%20response%20the%20Client%20will%20now%20receive%20a%20401%20Unauthorized%20message%20again%20and%20the%20server%20will%20again%20ask%20the%20client%20to%20authenticate%20itself.%20Here%20the%20ONLY%20method%20of%20authentication%20that%20is%20available%20is%20TLS-DSK%20(Cert%20based%20authentication)%20The%20SFB%20online%20server%20will%20provide%20the%20Client%20a%20Cert%20provisioning%20URL%20in%20the%20401%20you%20can%20see%20that%20in%20the%20snippet%20below%20This%20means%20that%20the%20Client%20now%20needs%20to%20present%20a%20Certificate%20that%20can%20then%20be%20used%20to%20authenticate%20the%20client.%20Since%20this%20is%20the%20first%20time%20the%20client%20is%20signing%20in%20it%20will%20NOT%20have%20the%20certificate%20installed.%20This%20certificate%20is%20ideally%20downloaded%20after%20the%20client%20signs%20in%20for%20the%20first%20time%20and%20is%20valid%20for%20about%208%20hours.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Since%20the%20client%20does%20not%20have%20a%20valid%20certificate%20it%20now%20has%20to%20Re-Authenticate%20to%20the%20Cert%20provisioning%20service.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20Process%20for%20this%20will%20again%20be%20the%20same%2C%20the%20client%20has%20to%20first%20get%20a%20Web%20ticket%2C%20to%20get%20a%20web%20ticket%20it%20needs%20to%20get%20a%20Token%20from%20O365%20AD%2C%20but%20we%20know%20that%20the%20client%20has%20already%20done%20these%20steps%20earlier.%20SO%20it%20already%20has%20a%20Web%20Ticket%20from%20the%20Web%20services%20URL.%20The%20Client%20needs%20to%20submit%20this%20same%20web%20ticket%20that%20it%20had%20obtained%20now%20to%20the%20Cert%20provisioning%20Service%20and%20once%20it%20submits%20the%20web%20ticket%20it%20will%20serve%20as%20a%20proof%20of%20authentication.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20Client%20learns%20about%20this%20by%20first%20sending%20a%20Mex%20request%20to%20the%20Cert%20provisioning%20URL.%20You%20can%20see%20that%20in%20the%20Trace%20below%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20alt%3D%22clip_image012%5B3%5D%22%20border%3D%220%22%20height%3D%22704%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115325i4ADDCF79E0EFAB99%22%20title%3D%22clip_image012%5B3%5D%22%20width%3D%221222%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20The%20Client%20then%20submits%20the%20Web%20Ticket%20that%20it%20had%20received%20to%20the%20Cert%20provisioning%20URL%20it%20received%20above%2C%20after%20this%20it%20receives%20a%20200%20OK%20and%20sign%20in%20is%20now%20complete%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20alt%3D%22clip_image013%5B3%5D%22%20border%3D%220%22%20height%3D%22712%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115326iA4D4607B833A54FE%22%20title%3D%22clip_image013%5B3%5D%22%20width%3D%221227%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Sign%20in%20is%20now%20complete!!%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20__________________________________________________________________________________________________________________________________________%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20More%20Information%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Detailed%20log%20snippets%20showing%20the%20client%20requesting%20and%20receiving%20Token%20from%20Org%20ID%20and%20ADFS.%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We%20Discussed%20above%20that%20in%20order%20to%20obtain%20a%20webticket%20the%20Client%20has%20to%20get%20authenticated%20with%20O365%20AD.%20We%20described%20this%20process%20as%20below%20%3CBR%20%2F%3E%3COL%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20first%20tries%20to%20reach%20Org%20ID%20(O365%20AD)%20to%20request%20a%20Token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EHere%20it%20learns%20that%20the%20tenant%20is%20enabled%20for%20ADFS%20so%20it%20has%20to%20now%20go%20to%20the%20ADFS%20URL%20first%20and%20ask%20for%20a%20token%20from%20ADFS%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20reaches%20out%20to%20ADFS%20and%20requests%20a%20Token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EADFS%20will%20challenge%20for%20authentication%20which%20will%20cause%20a%20Password%20prompt%20to%20appear%2C%20or%20the%20user%20credential%20stored%20in%20the%20credential%20manager%20will%20be%20passed%20to%20ADFS%20in%20which%20case%20the%20user%20will%20not%20be%20prompted%20for%20password%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EOnce%20the%20password%20is%20provided%20ADFS%20will%20provide%20the%20client%20a%20Token%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20client%20will%20then%20submit%20this%20token%20back%20to%20Org%20ID%20(O365%20AD)%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EOrg%20ID%20will%20in%20turn%20provide%20the%20client%20the%20Org%20ID%20token%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FOL%3E%3CBR%20%2F%3E%20%3CSTRONG%3E%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20We%20can%20see%20this%20in%20the%20IDCRL%20Logs%20which%20are%20located%20on%20the%20Client%20PC%20in%20the%20MSOTrace%20folder%20on%20the%20C%3A%5CDrive.%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Below%20are%20snippets%20from%20IDCRL%20logs%20showing%20all%20the%20above%20steps%20in%20detail%20for%20reference.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EBelow%20is%20the%20Client%20finding%20out%20that%20it%20needs%20to%20go%20to%20ADFS%20URL%20to%20authenticate%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREALMINFO%20success%3D%22%26quot%3Btrue%26quot%3B%22%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CLOGIN%3Enj%40johnsondatasystems.com%3C%2FLOGIN%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CNAMESPACETYPE%3EFederated%3C%2FNAMESPACETYPE%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CDOMAINNAME%3EJOHNSONDATASYSTEMS.COM%3C%2FDOMAINNAME%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CFEDERATIONGLOBALVERSION%3E-1%3C%2FFEDERATIONGLOBALVERSION%3E%3CAUTHURL%3E%3CA%20href%3D%22https%3A%2F%2Fsts.johnsondatasystems.com%2Fadfs%2Fls%2F%26lt%3B%2FAuthURL%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsts.johnsondatasystems.com%2Fadfs%2Fls%2F%3C%2FA%3E%3C%2FAUTHURL%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CISFEDERATEDNS%3Etrue%3C%2FISFEDERATEDNS%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTSAUTHURL%3E%3CA%20href%3D%22https%3A%2F%2Fsts.johnsondatasystems.com%2Fadfs%2Fservices%2Ftrust%2F2005%2Fusernamemixed%26lt%3B%2FSTSAuthURL%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsts.johnsondatasystems.com%2Fadfs%2Fservices%2Ftrust%2F2005%2Fusernamemixed%3C%2FA%3E%3C%2FSTSAUTHURL%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CFEDERATIONTIER%3E0%3C%2FFEDERATIONTIER%3E%3CFEDERATIONBRANDNAME%3EJOHNSONDATASYSTEMS.COM%3C%2FFEDERATIONBRANDNAME%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CALLOWFEDUSERSWLIDSIGNIN%3Efalse%3C%2FALLOWFEDUSERSWLIDSIGNIN%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CMEXURL%3E%3CA%20href%3D%22https%3A%2F%2Fsts.johnsondatasystems.com%2Fadfs%2Fservices%2Ftrust%2Fmex%26lt%3B%2FMEXURL%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsts.johnsondatasystems.com%2Fadfs%2Fservices%2Ftrust%2Fmex%3C%2FA%3E%3C%2FMEXURL%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSAML_AUTHURL%3E%3C%2FSAML_AUTHURL%3E%3CPREFERREDPROTOCOL%3E1%3C%2FPREFERREDPROTOCOL%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20The%20Client%20then%20sends%20a%20request%20to%20the%20ADFS%20URL%20to%20get%20a%20Token%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CHEADER%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CACTION%20mustunderstand%3D%22%26quot%3B1%26quot%3B%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FRST%2FIssue%26lt%3B%2Fwsa%3AAction%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FRST%2FIssue%3C%2FA%3E%3C%2FACTION%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CTO%20mustunderstand%3D%22%26quot%3B1%26quot%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fsts.johnsondatasystems.com%3A443%2Fadfs%2Fservices%2Ftrust%2F2005%2Fusernamemixed%26lt%3B%2Fwsa%3ATo%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsts.johnsondatasystems.com%3A443%2Fadfs%2Fservices%2Ftrust%2F2005%2Fusernamemixed%3C%2FA%3E%3C%2FTO%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CMESSAGEID%3E1507666614%3C%2FMESSAGEID%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSECURITY%3E%3CUSERNAMETOKEN%20id%3D%22%26quot%3Buser%26quot%3B%22%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CUSERNAME%3Enj%40johnsondatasystems.com%3C%2FUSERNAME%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CPASSWORD%3E*********%3C%2FPASSWORD%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FUSERNAMETOKEN%3E%3CTIMESTAMP%20id%3D%22%26quot%3BTimestamp%26quot%3B%22%3E%3CCREATED%3E2017-10-10T20%3A16%3A53Z%3C%2FCREATED%3E%3CEXPIRES%3E2017-10-10T20%3A21%3A53Z%3C%2FEXPIRES%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FTIMESTAMP%3E%3C%2FSECURITY%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FHEADER%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTSECURITYTOKEN%20id%3D%22%26quot%3BRST0%26quot%3B%22%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTTYPE%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FIssue%26lt%3B%2Fwst%3ARequestType%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FIssue%3C%2FA%3E%3C%2FREQUESTTYPE%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CAPPLIESTO%3E%3CENDPOINTREFERENCE%3E%3CADDRESS%3Eurn%3Afederation%3AMicrosoftOnline%3C%2FADDRESS%3E%3C%2FENDPOINTREFERENCE%3E%3C%2FAPPLIESTO%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CKEYTYPE%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F05%2Fidentity%2FNoProofKey%26lt%3B%2Fwst%3AKeyType%26gt%3B%26lt%3B%2Fwst%3ARequestSecurityToken%26gt%3B%26lt%3B%2Fs%3ABody%26gt%3B%26lt%3B%2Fs%3AEnvelope%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F05%2Fidentity%2FNoProofKey%3C%2FA%3E%3C%2FKEYTYPE%3E%3C%2FREQUESTSECURITYTOKEN%3E%3C%2FREALMINFO%3E%3C%2FLINGO-BODY%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20It%20will%20then%20receive%20the%20Token%20from%20ADFS%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTSECURITYTOKENRESPONSE%20t%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%3C%2FA%3E%22%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CLIFETIME%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CCREATED%20wsu%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fdocs.oasis-open.org%2Fwss%2F2004%2F01%2Foasis-200401-wss-wssecurity-utility-1.0.xsd%26quot%3B%26gt%3B2017-10-10T20%3A16%3A55.065Z%26lt%3B%2Fwsu%3ACreated%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fdocs.oasis-open.org%2Fwss%2F2004%2F01%2Foasis-200401-wss-wssecurity-utility-1.0.xsd%26quot%3B%26gt%3B2017-10-10T20%3A16%3A55.065Z%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fdocs.oasis-open.org%2Fwss%2F2004%2F01%2Foasis-200401-wss-wssecurity-utility-1.0.xsd%22%26gt%3B2017-10-10T20%3A16%3A55.065Z%3C%2FA%3E%3C%2FCREATED%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CEXPIRES%20wsu%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fdocs.oasis-open.org%2Fwss%2F2004%2F01%2Foasis-200401-wss-wssecurity-utility-1.0.xsd%26quot%3B%26gt%3B2017-10-10T21%3A16%3A55.065Z%26lt%3B%2Fwsu%3AExpires%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fdocs.oasis-open.org%2Fwss%2F2004%2F01%2Foasis-200401-wss-wssecurity-utility-1.0.xsd%26quot%3B%26gt%3B2017-10-10T21%3A16%3A55.065Z%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fdocs.oasis-open.org%2Fwss%2F2004%2F01%2Foasis-200401-wss-wssecurity-utility-1.0.xsd%22%26gt%3B2017-10-10T21%3A16%3A55.065Z%3C%2FA%3E%3C%2FEXPIRES%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FLIFETIME%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CAPPLIESTO%20wsp%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2004%2F09%2Fpolicy%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2004%2F09%2Fpolicy%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2004%2F09%2Fpolicy%3C%2FA%3E%22%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CENDPOINTREFERENCE%20wsa%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fwww.w3.org%2F2005%2F08%2Faddressing%26quot%3B%26gt%3B%26lt%3Bwsa%3AAddress%26gt%3Burn%3Afederation%3AMicrosoftOnline%26lt%3B%2Fwsa%3AAddress%26gt%3B%26lt%3B%2Fwsa%3AEndpointReference%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fwww.w3.org%2F2005%2F08%2Faddressing%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.w3.org%2F2005%2F08%2Faddressing%3C%2FA%3E%22%26gt%3B%3CADDRESS%3Eurn%3Afederation%3AMicrosoftOnline%3C%2FADDRESS%3E%3C%2FENDPOINTREFERENCE%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FAPPLIESTO%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTEDSECURITYTOKEN%3E**********%3C%2FREQUESTEDSECURITYTOKEN%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Once%20the%20Client%20receives%20the%20Token%20from%20ADFS%20it%20then%20submits%20this%20token%20to%20O365%20AD%20(Org%20ID)%20and%20requests%20a%20token%20from%20Org%20ID%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Below%20is%20the%20request%20that%20the%20client%20sends%20to%20Org%20ID%20asking%20for%20a%20token%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CHEADER%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CACTION%20mustunderstand%3D%22%26quot%3B1%26quot%3B%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FRST%2FIssue%26lt%3B%2Fwsa%3AAction%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FRST%2FIssue%3C%2FA%3E%3C%2FACTION%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CTO%20mustunderstand%3D%22%26quot%3B1%26quot%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%3A443%2Frst2.srf%26lt%3B%2Fwsa%3ATo%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%3A443%2Frst2.srf%3C%2FA%3E%3C%2FTO%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CMESSAGEID%3E1507666615%3C%2FMESSAGEID%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CAUTHINFO%20ps%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2FPassport%2FSoapServices%2FPPCRL%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2FPassport%2FSoapServices%2FPPCRL%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2FPassport%2FSoapServices%2FPPCRL%3C%2FA%3E%22%20Id%3D%22PPAuthInfo%22%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CHOSTINGAPP%3E%7B0000003F-002B-0000-4C0A-AE614E000000%7D%3C%2FHOSTINGAPP%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBINARYVERSION%3E7%3C%2FBINARYVERSION%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CUIVERSION%3E1%3C%2FUIVERSION%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CCOOKIES%3E%3C%2FCOOKIES%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTPARAMS%3EAQAAAAIAAABsYwQAAAAxMDMz%3C%2FREQUESTPARAMS%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FAUTHINFO%3E%3CSECURITY%3E*********%3C%2FSECURITY%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FHEADER%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTMULTIPLESECURITYTOKENS%20ps%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2FPassport%2FSoapServices%2FPPCRL%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2FPassport%2FSoapServices%2FPPCRL%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2FPassport%2FSoapServices%2FPPCRL%3C%2FA%3E%22%20Id%3D%22RSTS%22%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTSECURITYTOKEN%20id%3D%22%26quot%3BRST0%26quot%3B%22%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTTYPE%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FIssue%26lt%3B%2Fwst%3ARequestType%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FIssue%3C%2FA%3E%3C%2FREQUESTTYPE%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CAPPLIESTO%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CENDPOINTREFERENCE%3E%3CADDRESS%3E%3CA%20href%3D%22http%3A%2F%2FPassport.NET%2Ftb%26lt%3B%2Fwsa%3AAddress%26gt%3B%26lt%3B%2Fwsa%3AEndpointReference%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2FPassport.NET%2Ftb%3C%2FA%3E%3C%2FADDRESS%3E%3C%2FENDPOINTREFERENCE%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FAPPLIESTO%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FREQUESTSECURITYTOKEN%3E%3CREQUESTSECURITYTOKEN%20id%3D%22%26quot%3BRST1%26quot%3B%22%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTTYPE%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FIssue%26lt%3B%2Fwst%3ARequestType%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F02%2Ftrust%2FIssue%3C%2FA%3E%3C%2FREQUESTTYPE%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CAPPLIESTO%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CENDPOINTREFERENCE%3E%3CADDRESS%3E%3CA%20href%3D%22https%3A%2F%2Fwebpooldm12a05.infra.lync.com%2FWebTicket%2FWebTicketAdvancedService.svc%2FWsFed_bearer%26lt%3B%2Fwsa%3AAddress%26gt%3B%26lt%3B%2Fwsa%3AEndpointReference%26gt%3B%26lt%3B%2Fwsp%3AAppliesTo%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebpooldm12a05.infra.lync.com%2FWebTicket%2FWebTicketAdvancedService.svc%2FWsFed_bearer%3C%2FA%3E%3C%2FADDRESS%3E%3C%2FENDPOINTREFERENCE%3E%3C%2FAPPLIESTO%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FREQUESTSECURITYTOKEN%3E%3C%2FREQUESTMULTIPLESECURITYTOKENS%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Org%20ID%20then%20issues%20a%20Token%20to%20the%20client%20which%20we%20can%20see%20below%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTEDPROOFTOKEN%3E%3CBINARYSECRET%3Ex5hTCJZbYuSHUl0mKtoAab%2FzN4DE%2BYLW%3C%2FBINARYSECRET%3E%3C%2FREQUESTEDPROOFTOKEN%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FREQUESTSECURITYTOKENRESPONSE%3E%3CREQUESTSECURITYTOKENRESPONSE%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CTOKENTYPE%3Eurn%3Aoasis%3Anames%3Atc%3ASAML%3A1.0%3C%2FTOKENTYPE%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CAPPLIESTO%20wsa%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fwww.w3.org%2F2005%2F08%2Faddressing%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fwww.w3.org%2F2005%2F08%2Faddressing%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.w3.org%2F2005%2F08%2Faddressing%3C%2FA%3E%22%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CENDPOINTREFERENCE%3E%3CADDRESS%3E%3CA%20href%3D%22https%3A%2F%2Fwebpooldm12a05.infra.lync.com%2FWebTicket%2FWebTicketAdvancedService.svc%2FWsFed_bearer%26lt%3B%2Fwsa%3AAddress%26gt%3B%26lt%3B%2Fwsa%3AEndpointReference%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebpooldm12a05.infra.lync.com%2FWebTicket%2FWebTicketAdvancedService.svc%2FWsFed_bearer%3C%2FA%3E%3C%2FADDRESS%3E%3C%2FENDPOINTREFERENCE%3E%26gt%3B%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3C%2FAPPLIESTO%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CLIFETIME%3E%3CCREATED%3E2017-10-10T20%3A16%3A56Z%3C%2FCREATED%3E%3CEXPIRES%3E2017-10-11T04%3A16%3A56Z%3C%2FEXPIRES%3E%3C%2FLIFETIME%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CREQUESTEDSECURITYTOKEN%3E**********%3C%2FREQUESTEDSECURITYTOKEN%3E%3C%2FREQUESTSECURITYTOKENRESPONSE%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-621263%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Apr%2009%2C%202018%20Scenario%3A%20Pure%20Online%20(O365)%20environment%2C%20SFB%20user%20is%20homed%20Online%2C%20ADFS%20is%20Configured%2C%20MA%20(Modern%20Auth)%20is%20Disabled%20in%20O365NOTE%3AI%20have%20tried%20my%20best%20to%20ensure%20the%20information%20below%20is%20accurate.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-621263%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eadfs%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENextHop%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESfB%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esfb%20client%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esign%20in%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
First published on TECHNET on Apr 09, 2018
Scenario: Pure Online (O365) environment, SFB user is homed Online, ADFS is Configured, MA (Modern Auth) is Disabled in O365

NOTE:

I have tried my best to ensure the information below is accurate. Some of the terms I use to describe things like Modern Auth provider, O365 AD, Org ID etc. may not be standard terminology, I use them solely to make the understanding simpler. 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.

How Does it Work?

Below is a High level explanation on how the SFB online Client Sign in process works

clip_image001[4]

SIP URI of the user - NJ@JohnsonDataSystems.com

  1. SFB client Queries DNS for Lyncdiscover.domain.com. This should point to Webdir.online.lync.com

  2. SFB Client then sends a unauthenticated GET request to Lyncdiscover.domain.com

  3. The Client is then redirected to Autodiscover https://webdir2a.online.lync.com/Autodiscover/AutodiscoverService.svc/root/user?originalDomain...

  4. SFB Client then sends a Request to Autodiscover to discover its pool for sign in.

  5. The Client is then challenged and is provided the URL for Webticket service ( https://webdir2a.online.lync.com/WebTicket/WebTicketService.svc ) where it can request a Webticket

  6. The Client then sends a POST request to Webticket Service which requires the client to provide a Token from Org ID (login.microsoftonline.com)

  7. Now in order to authenticate the client reaches out to Ord ID and requests a Token

  8. Since the tenant is enabled for ADFS the client is redirected to the ON Premise ADFS server https://sts.cloudsfb.com

  9. SFB client will then send a request to ADFS server and request a token

  10. The Client may receive a Password prompt (or previously saved password from credential manager is passed) and once the correct password is provided, ADFS will issue a Token to the client

  11. The Client then submits this token to Org ID

  12. ORG ID will now issue its own Token to the client

  13. The Client then submits this token that it received from ORG ID to Webticket Service

  14. Webticket service now will grant a Webticket to the Client

  15. The client then submits this webticket to Autodiscover

  16. In Response Autodiscover will provide the Pool names (sipfed2a.online.lync.com" port="443) where the client can send Register to Sign in

  17. The SFB client now sends a SIP register to the Online Edge pool (sipfed2a.online.lync.com" port="443)

  18. It is then challenged for authentication again, here the ONLY supported method of authentication is TLS-DSK, The client is provided a Cert provisioning URL ( https://webdir2a.online.lync.com:443/CertProv/CertProvisioningService.svc ) in the 401 unauthenticated response

  19. The SFB client then sends a request to Certprov

  20. Here again the Client is challenged for authentication and is redirected to webticket service to get Webticket

  21. The Client had already Obtained a webticket in step 14 above

  22. The client will submit the same webticket obtained in step 14 to the Cert provisioning service

  23. The Client then receives a certificate

  24. The SFB client can now send a Register again and use the certificate it downloaded for authentication


Below is a graphical representation of the SFB online Client Sign in process

clip_image002[4]

Detailed Explanation of SFB online Client Sign in process with LOG Snippets:

SIP URI of the user - NJ@JohnsonDataSystems.com

When a SFB client wants to Sign in, It needs to know where it can send its request to be able to Sign in. Whenever a user enters his SIP URI to sign in the SFB client forms an autodiscover URL using the domain name that it extracts from the users SIP URI to start the discovery process and then it sends an Unauthenticated Get request to the URL, lyncdiscover.domain.com. The response code for this request will be '200 ok' and in the response we should receive the external webservices URL for autodiscover.

You can see the request and Response below

clip_image003[4]

The SFB Client learns that it needs to Contact https://webdir2a.online.lync.com/

It then tries to Do a TCP handshake with webdir2a.online.lync.com, Followed by a TLS handshake. (I haven't included the TCP and TLS handshake screen shots here, you can see those if you collect a Network trace while signing in)

The client then sends a request to the Autodiscover URL for its own domain (in my case @ JohnsonDataSystems.com ) and in Response it receives the Autodiscover URL's specific to the users Tenant. You can see the request and Response below

clip_image004[4]

The client then sends a request to the user URL. We are here trying to discover a specific users home pool, hence the request will go to the “User” URL.

In the response, the Client receives a Web ticket URL, which provides the location of the WebTicketService.

You can see the request and Response below

clip_image005[4]

The Client then needs to send a Request to the Web ticket service URL in order to obtain a Web ticket. The client will send this request in a POST message to the web ticket Service and in response it receives the actual individual Web ticket service URL's

clip_image006[3]

The Client has to submit a Request to this web ticket URL now in order to obtain a web ticket. But if it does that then it will need to authenticate first, unless the Client authenticates itself it will not be issued a web ticket. Since this user is Homed in SFB online the Client needs to reach out to O35 AD (Org ID) to get authenticated first

SO right now the Client has to First reach out to Org ID in order to authenticate and Get a Token.

The process of reaching out to Org ID is initiated with the help of Microsoft Online Sign in Assistant (also known as IDCRL) that is installed on the Computer.

You may not always see this in the fiddler trace, this attempt to get Token from AD is called Org ID auth and is captured in IDCRL logs on the client PC

The Client will try to reach Org ID (O365 AD) to get a token, but since the Tenant is Enabled for ADFS the O365 AD (org ID) will redirect the client to the ADFS Server URL and the client will have to request a Token from ADFS

The way this works is

  1. The client first tries to reach Org ID (O365 AD) to request a Token

  2. Here it learns that the tenant is enabled for ADFS so it has to now go to the ADFS URL first and ask for a token from ADFS

  3. The client reaches out to ADFS and requests a Token

  4. ADFS will challenge for authentication which will cause a Password prompt to appear, or the user credential stored in the credential manager will be passed to ADFS in which case the user will not be prompted for password

  5. Once the password is provided ADFS will provide the client a Token

  6. The client will then submit this token back to Org ID (O365 AD)

  7. Org ID will in turn provide the client the Org ID token


You can view all the above if you open the IDCRL log (MSOTrace folder) in the IDCRL parser, A successful token retrieval from ADFS and Org ID should look like below in the Parser (A more detailed explanation can be found in the bottom of this document if needed for reference)

clip_image007[3]

Once the Client receives a Token from O365 AD (Org ID) it then submits this token to the Web Ticket Service https://webdir2a.online.lync.com/WebTicket/WebTicketAdvancedService.svc/WsFed_bearer

In Response the Web Ticket Service will now Issue the Client a Web Ticket. You can see this in the Trace below

clip_image008[3]

The Client will Then Submit this web ticket back to the AutoDiscover User URL - https://webdir2a.online.lync.com/Autodiscover/AutodiscoverService.svc/root/user?originalDomain=j...

In response it will now receive the Internal and External addresses of the Pool names where the user is Homed.

You can see this in the trace below

clip_image009[3]

Once the Client receives the pool names it will then Send a SIP REGISTER message to the SFB pool in order to sign in. . You can see that in the Client UCCAPI log file. This is shown in the snippet below

clip_image010[3]

In response the Client will now receive a 401 Unauthorized message again and the server will again ask the client to authenticate itself. Here the ONLY method of authentication that is available is TLS-DSK (Cert based authentication)

The SFB online server will provide the Client a Cert provisioning URL in the 401 you can see that in the snippet below

clip_image011[3]

This means that the Client now needs to present a Certificate that can then be used to authenticate the client. Since this is the first time the client is signing in it will NOT have the certificate installed. This certificate is ideally downloaded after the client signs in for the first time and is valid for about 8 hours.

Since the client does not have a valid certificate it now has to Re-Authenticate to the Cert provisioning service.

The Process for this will again be the same, the client has to first get a Web ticket, to get a web ticket it needs to get a Token from O365 AD, but we know that the client has already done these steps earlier. SO it already has a Web Ticket from the Web services URL. The Client needs to submit this same web ticket that it had obtained now to the Cert provisioning Service and once it submits the web ticket it will serve as a proof of authentication.

The Client learns about this by first sending a Mex request to the Cert provisioning URL. You can see that in the Trace below

clip_image012[3]

The Client then submits the Web Ticket that it had received to the Cert provisioning URL it received above, after this it receives a 200 OK and sign in is now complete

clip_image013[3]

Sign in is now complete!!

__________________________________________________________________________________________________________________________________________



More Information:

Detailed log snippets showing the client requesting and receiving Token from Org ID and ADFS.

We Discussed above that in order to obtain a webticket the Client has to get authenticated with O365 AD. We described this process as below

  1. The client first tries to reach Org ID (O365 AD) to request a Token

  2. Here it learns that the tenant is enabled for ADFS so it has to now go to the ADFS URL first and ask for a token from ADFS

  3. The client reaches out to ADFS and requests a Token

  4. ADFS will challenge for authentication which will cause a Password prompt to appear, or the user credential stored in the credential manager will be passed to ADFS in which case the user will not be prompted for password

  5. Once the password is provided ADFS will provide the client a Token

  6. The client will then submit this token back to Org ID (O365 AD)

  7. Org ID will in turn provide the client the Org ID token




We can see this in the IDCRL Logs which are located on the Client PC in the MSOTrace folder on the C:\Drive.

Below are snippets from IDCRL logs showing all the above steps in detail for reference.



Below is the Client finding out that it needs to go to ADFS URL to authenticate



<?xml version="1.0" encoding="UTF-8"?><RealmInfo Success="true">

<Login>nj@johnsondatasystems.com</Login>

<NameSpaceType>Federated</NameSpaceType>

<DomainName>JOHNSONDATASYSTEMS.COM</DomainName>

<FederationGlobalVersion>-1</FederationGlobalVersion><AuthURL>https://sts.johnsondatasystems.com/adfs/ls/</AuthURL>

<IsFederatedNS>true</IsFederatedNS>

<STSAuthURL>https://sts.johnsondatasystems.com/adfs/services/trust/2005/usernamemixed</STSAuthURL>

<FederationTier>0</FederationTier><FederationBrandName>JOHNSONDATASYSTEMS.COM</FederationBrandName>

<AllowFedUsersWLIDSignIn>false</AllowFedUsersWLIDSignIn>

<MEXURL>https://sts.johnsondatasystems.com/adfs/services/trust/mex</MEXURL>

<SAML_AuthURL></SAML_AuthURL><PreferredProtocol>1</PreferredProtocol>



The Client then sends a request to the ADFS URL to get a Token

<s:Header>

<wsa:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue</wsa:Action>

<wsa:To s:mustUnderstand="1">https://sts.johnsondatasystems.com:443/adfs/services/trust/2005/usernamemixed</wsa:To>

<wsa:MessageID>1507666614</wsa:MessageID>

<wsse:Security><wsse:UsernameToken wsu:Id="user">

<wsse:Username>nj@johnsondatasystems.com</wsse:Username>

<wsse:Password>*********</wsse:Password>

</wsse:UsernameToken><wsu:Timestamp Id="Timestamp"><wsu:Created>2017-10-10T20:16:53Z</wsu:Created><wsu:Expires>2017-10-10T20:21:53Z</wsu:Expires>

</wsu:Timestamp></wsse:Security>

</s:Header>

<wst:RequestSecurityToken Id="RST0">

<wst:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue</wst:RequestType>

<wsp:AppliesTo><wsa:EndpointReference><wsa:Address>urn:federation:MicrosoftOnline</wsa:Address></wsa:EndpointReference></wsp:AppliesTo>

<wst:KeyType>http://schemas.xmlsoap.org/ws/2005/05/identity/NoProofKey</wst:KeyType></wst:RequestSecurityToken></...>

It will then receive the Token from ADFS

<s:Body>

<t:RequestSecurityTokenResponse xmlns:t="http://schemas.xmlsoap.org/ws/2005/02/trust">

<t:Lifetime>

<wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2017-10-10T20:16...>

<wsu:Expires xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2017-10-10T21:16...>

</t:Lifetime>

<wsp:AppliesTo xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">

<wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:Address>urn:federation:MicrosoftOnline</wsa:Address></wsa...>

</wsp:AppliesTo>

<t:RequestedSecurityToken>**********</t:RequestedSecurityToken>



Once the Client receives the Token from ADFS it then submits this token to O365 AD (Org ID) and requests a token from Org ID

Below is the request that the client sends to Org ID asking for a token

<s:Header>

<wsa:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue</wsa:Action>

<wsa:To s:mustUnderstand="1">https://login.microsoftonline.com:443/rst2.srf</wsa:To>

<wsa:MessageID>1507666615</wsa:MessageID>

<ps:AuthInfo xmlns:ps="http://schemas.microsoft.com/Passport/SoapServices/PPCRL" Id="PPAuthInfo">

<ps:HostingApp>{0000003F-002B-0000-4C0A-AE614E000000}</ps:HostingApp>

<ps:BinaryVersion>7</ps:BinaryVersion>

<ps:UIVersion>1</ps:UIVersion>

<ps:Cookies></ps:Cookies>

<ps:RequestParams>AQAAAAIAAABsYwQAAAAxMDMz</ps:RequestParams>

</ps:AuthInfo><wsse:Security>*********</wsse:Security>

</s:Header>

<s:Body>

<ps:RequestMultipleSecurityTokens xmlns:ps="http://schemas.microsoft.com/Passport/SoapServices/PPCRL" Id="RSTS">

<wst:RequestSecurityToken Id="RST0">

<wst:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue</wst:RequestType>

<wsp:AppliesTo>

<wsa:EndpointReference><wsa:Address>http://Passport.NET/tb</wsa:Address></wsa:EndpointReference>

</wsp:AppliesTo>

</wst:RequestSecurityToken><wst:RequestSecurityToken Id="RST1">

<wst:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue</wst:RequestType>

<wsp:AppliesTo>

<wsa:EndpointReference><wsa:Address>https://webpooldm12a05.infra.lync.com/WebTicket/WebTicketAdvancedService.svc/WsFed_bearer</wsa:Addre...>

</wst:RequestSecurityToken></ps:RequestMultipleSecurityTokens>

</s:Body>



Org ID then issues a Token to the client which we can see below

<wst:RequestedProofToken><wst:BinarySecret>x5hTCJZbYuSHUl0mKtoAab/zN4DE+YLW</wst:BinarySecret></wst:RequestedProofToken>

</wst:RequestSecurityTokenResponse><wst:RequestSecurityTokenResponse>

<wst:TokenType>urn:oasis:names:tc:SAML:1.0</wst:TokenType>

<wsp:AppliesTo xmlns:wsa="http://www.w3.org/2005/08/addressing">

<wsa:EndpointReference><wsa:Address>https://webpooldm12a05.infra.lync.com/WebTicket/WebTicketAdvancedService.svc/WsFed_bearer</wsa:Addre...>

</wsp:AppliesTo>

<wst:Lifetime><wsu:Created>2017-10-10T20:16:56Z</wsu:Created><wsu:Expires>2017-10-11T04:16:56Z</wsu:Expires></wst:Lifetime>

<wst:RequestedSecurityToken>**********</wst:RequestedSecurityToken>