How the session will work in multiple server environment? in SharePoint?
ans) SP uses the security Token Service (STS) to create Security Assertion Markup Language(SAML) tokes. both claims-based web appl and inter-farm communication use
STS. The logon tokens cache stores the security token, know as a cliam or a fedauth token that is issued by STS for use by any web server in the server farm. Any web
server that receives a request for resources can access the security token from the cache, authenticate the user, and provide access to the resources requested.
Every time a user accesses a web server, the user needs to be authenticated which can become an issue in multiple web servers.
In sp2010 to ensure that the user stayed on the same web server, load balancing affinity-known as sticky sessions- was enabled.
By caching the FebAuth token in the distributed cache, it is no longer necessary to enable sticky sessions, because the authentication token is now available
from all web servers through the cache cluster.
ans) SP uses the security Token Service (STS) to create Security Assertion Markup Language(SAML) tokes. both claims-based web appl and inter-farm communication use
STS. The logon tokens cache stores the security token, know as a cliam or a fedauth token that is issued by STS for use by any web server in the server farm. Any web
server that receives a request for resources can access the security token from the cache, authenticate the user, and provide access to the resources requested.
Every time a user accesses a web server, the user needs to be authenticated which can become an issue in multiple web servers.
In sp2010 to ensure that the user stayed on the same web server, load balancing affinity-known as sticky sessions- was enabled.
By caching the FebAuth token in the distributed cache, it is no longer necessary to enable sticky sessions, because the authentication token is now available
from all web servers through the cache cluster.
