That's right, here it goes - this is the long answer ...
The problem with this will be that saving the SID will not be sufficient to be able to re-authenticate the user if you need to perform an action on their behalf (that is, impersonate this user) - for this you will need the Software token provided by the operating system . If you only have a SID, you still need a password in this scenario - if you are not using reversible encryption in your AD repository, I seriously doubt it, and, of course, hope it is not!
, , , , SID , - ( , HTTPS ), .
- SID , .
, AD , Negotiate Kerberos. , ; , ( ).
, , - - , , .
, , , , . -, , ( - ). , :
AD , , , AD SID - - . , , , .
, (nonce - , wikipedia. RNGCryptoServiceProvider ). ( ) (ip, ) .
, , , , , Rijndael SymmetricAlgorithm 128- IV 256- ( , RNG!).
, ( - ).
,
- , , , , .
- , , , , . - , . , , 403. , , , .
- , .
, HTTP , .
, - .. , . ; , .
∞
( )
, , - , .
HTTPS , , . , , , , . HTTPS .
, , , , IP- . , , HTTP.
, , - - , .
, , 12- - , , , 12- , , .
- , / , , , :)