There is a lot of information around AD FS and several suggestions that involve playing with the TokenLifetime, Freshness, and WebSSOLifetime settings. Are there any best practice when it comes to handling when a token is expired?
We have a custom application using ASP.Net that uses AD FS 2.0 as it's authentication. Everything seems to work fine, unless you leave the site idle too long. We're noticing errors related to authentication. From what I can tell, it seems like the token is expired.
Reloading the page would cause the login to pop and everything works fine after you reenter the login information.
This is the example we've used to create the application:
http://blogs.msdn.com/b/alextch/archive/2011/06/27/building-a-test-claims-aware-asp-net-application-and-integrating-it-with-adfs-2-0-security-token-service-sts.aspx
I'm not able to find a good clean example of a simple application what demonstrates how a base AD FS 2.0 enabled application would work.