wif - Single Sign Off do not clear RP's own session -

-

I'm new to wif and now I have to face a problem when a single sign is turned off.

The following is the background of my problem: First of all, I am working on two old A and B, which they store the user's information in it, after authenticating a user, their own sessions Variable And App A and B have their own local database. Now, my job is to use ADFS to enable SSO (Single Signon) between two applications.

Now, I am creating a new Active Directory to store users centrally, when a user tries to log into the application A through ADFS, then the application can be used in the local names Need to check. If present, the user can log in to the AP. Otherwise, the app will reject the claim.

Here is the technical section:

I extend the WSFAdationActection module and check the incoming claim methodology onSessionSecurityTokenCreated in the local database. If the result is matched, then I retrieve the user's information from the local database and store it in the session variable (so that I can reduce the code change). App B uses the same approach.

I am happy with the SSO from here. But the problem comes when I sign off:

When I log out of App A, I first clear my session in App A and call the WSFederationAuthenticationModule.FederatedSignOut method . However, App B does not clear its own session. I think that OnSignedOut will be implemented in the WSFederationAuthenticationModule. How can I clear the App B session when I signed the App B?

This can be very confusing. If you get confused things or need more clarification then please leave a comment.

Sign-out has been implemented in WS-FED by ADFS (this app /? W = wsignoutcleanup1 .0), not only locally this is the only way to notify the other app, with sign up, your app must be redirected to ADFS, then both apps will be notified and their session will be notified Can clear the situation (with gif request)


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more