Closed GoogleCodeExporter closed 9 years ago
Hi Deepak,
Could you please take a look at this ?
Original comment by l...@3pillarglobal.com
on 16 Aug 2012 at 11:11
A possible reason could be that session at STS are not cleaned up andit assumes
user is already logged in. One thing you could try is to call LogOut() method
in STS code just before redirecting user to SP. This would force SocialAuth.NET
to always move up to provider. If user is logged in to that provider, login
popup won't come up else user will be redirected to provider.
Try this and let us know if this helps.
Deepak
Original comment by daggar...@brickred.com
on 18 Aug 2012 at 9:33
Here is the code which I have modified on STS, Default.aspx, Page_PreRender
event to make sure to logout completely on STS Provider. After I added the
following, it's working fine.
See the region added in the following section
else if ( action == WSFederationConstants.Actions.SignOut )
{
// Process signout request.
SignOutRequestMessage requestMessage = (SignOutRequestMessage)WSFederationMessage.CreateFromUri( Request.Url );
#region Added by VY - To signout completley.
if (SocialAuthUser.IsLoggedIn())
{
SocialAuthUser saUser = SocialAuthUser.GetCurrentUser();
saUser.Logout();
}
#endregion
FederatedPassiveSecurityTokenServiceOperations.ProcessSignOutRequest( requestMessage, User, requestMessage.Reply, Response );
}
Original comment by VSYarlag...@dmgov.org
on 20 Aug 2012 at 1:42
Glad the solution worked.
Thanks for updating the post with code change. I'll refer this from FAQ section.
Deepak
Original comment by daggar...@brickred.com
on 3 Sep 2012 at 8:47
Original issue reported on code.google.com by
VSYarlag...@dmgov.org
on 24 Jul 2012 at 9:13Attachments: