asp.net - Is it strictly necessary to implement a security token cache in a WIF + Web Farm scenario? -


we're trying implement wif in .net 4.5 web farm. using shared machine keys allow multiple nodes decrypt fedauth cookie. we're running issues , in process of debugging them.

as we've been looking blog posts/articles/docs describing wif + web farm configurations, see mentions of shared token caches. many describe caches beneficial performance or dealing too-large cookies. however, others seem suggest strictly necessary in order wif working at all. msdn article above:

in [a web farm] scenario, default wif settings ... not work because both token protection and token caching dependent on specific computer.

emphasis mine.

so, question is: strictly necessary implement shared token cache in order make wif work in web farm? if so, can me understand nature , purpose of cached data?

the token cache needed when want cache tokens on server.

the sam supports mode called "reference tokens" - using cookie contains identifier whereas actual principal (+ bootstrap context if used) cached on server.

wif's default implementation of cache local in-memory, shared cache requirements web farms. if reference mode used - not default.


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -