Do I need to use proc sessions when implementing SSO? What will be the inproc restriction? which is the best way to implement single sign-on in a domain?
Using inproc and persisted sessions has little to do with SSO. The main limitation of inproc sessions is that it will not work in a balanced setup, but again, it has little to do with SSO. The easiest way to implement SSO is to use the Windows Identity Foundation (WIF) , which is part of the .NET Framework 4.0 (there is also a version that works with .net 3.5). Basically you just implement passive STS . There are several passes.
, . , , - machineKey cookie .exampledomain.com web.configs.
, , , , SQL. , GetTempAppID, 1 machineKey . sheero. !
inproc , , SQL Server, , SSO, , , /, , - , , ASP.Net 2.0, , .Net , , , , . SSO , , , .
Source: https://habr.com/ru/post/1769093/More articles:Is native AAC decoder available when using Android NDK? - androidImage of click_link in a cucumber - ruby | fooobar.comHow to implement the Facebook friends module in the database? - javaHow to disable the encryption password? - ruby-on-railsChoosing from multiple tables in Rails - sqlDevelopment workflow for Heroku? - ruby | fooobar.comAndroid license check library offline - androidстатические элементы при использовании в синхронизированном методе или блоке в java - javaSpring Альтернативы MockHttpServlet (RequestUTF-8 string handling in C # web service - stringAll Articles