<html><head></head><body><div class="yahoo-style-wrap" style="font-family:lucida console, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div><div>We're having a problem with physical iOS devices (works fine on Chrome virtual device) where a final Seaside redirect is not happening after an Azure SSO redirect. </div><div>I'd like to understand what triggers the Seaside redirect: I can see it in normal rendering, but I've never had to dig into it like this before. </div><div><br></div><div>When I log from a non-iOS device I see...</div><div>1: WAApplication>>handleFiltered: application URL</div><div> - self requestContext redirectTo: 'https://login.microsoftonline.com/...' </div><div> - redirects back to our app URL with an access token</div><div>2: WAApplication>>handleFiltered: application URL with MS access token & no _s & _k values </div><div> - validate token with Azure </div><div> - save user info in new WASession </div><div> - finish render</div><div>3: WAApplication>>handleFiltered: application URL with _s & _k plus callback values like: &2=2160&1=3840&3=false </div><div> - WAResponse>>location: application URL with _s & new _k and no callback values </div><div>4: WAApplication>>handleFiltered: application URL with _s & _K </div><div> - finish render</div><div> </div><div>With iOS step 3 does not happen; I'd like to know what triggers it normally. </div><div><br></div><div>Just to add to the fun, we have a two WAApplication registered. The default application fails on iOS, the other works fine. I can see no obvious difference between the two. </div><div><br></div><div>Thanks for any help (I'll cross post on the the Seaside mailing list and Discord)</div></div><div><br></div><div dir="ltr" data-setdir="false">Bob Nemec</div><div dir="ltr" data-setdir="false"><br></div><br></div></div></body></html>