Per my requirements, I needed to integrate with the System.IdentityModel SessionAuthenticationModule/WSFederationAuthenticationModule. What I have happening now is the site gets loaded, sees the user is not authenticated, goes out to the third party URL and requests login. This works fine as I have implemented and have worked around handling log outs and token expiration, etc.
A new issue arose and that IE and sometimes even Chrome are caching the pages. Workflow goes like this: 1) User hits localhost/#/ and gets redirected to 3rd party to login. 2) User logs in and is redirected back to localhost/#/ 3) User logs out of site successfully and is directed to 3rd party site indicated successful logout. 4) User pastes http://localhost/#/ back into the browser, hits enter. The site is cached and they can move around and do whatever that is on the client. If they hit the server to make a REST call the authentication will fail and they will be booted. But I would definitely like it to not keep the page cached like that. What are my options here? Apologize if this sounds obvious but I am still new to Angular. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
