Reputation: 49
I am trying to callback a .net framework client action method after sign out. For this I am trying to send a PostLogoutRedirectUri from a client on sign out. Problem I am facing is when suppose I have two .net framework clients A and B on a same browser. If I log in from client A and try to logout from a same client I am able to get PostLogoutRedirectUri in identity server 4 LogOut due to correct id_token but When log in from client A and I try to logout from client B (already logged in and authorized) due to the different id_token of client A PostLogoutRedirectUri and LogOutId is null in identity server LogOut. Below are the screenshots of my code and what i am trying to do:
Client A
Client B
Scenarios
Login From Client A and Logout from same Client
screenshot identity server Logout
Login From Client A, open Client B (authorized) and logout from Client B
screenshot identity server Logout
Upvotes: 1
Views: 675
Reputation: 49
The problem was that client A and client B where using a same cookie generated by whichever client logins first. Cookie was being shared between both clients because both clients were running on same domain which is localhost so due to the same domain of different clients only single cookie was being generated. It was solved by giving cookie a different name in startup.cs of every client.
Upvotes: 1