iis - Automatic machine key generation in ASP.NET -


by default, machine key setting auto generate , per application (autogenerate,isolateapps). msdn states decryption key , validation key based on web application id. hosting 2 asp.net mvc 2 sites on iis 7 server found out machine key same. verified using reflection see validationkeyinternal , decryptionkeyinternal property. tested generating anti forgery token cookie on 1 site , pass other , cookie can read.

after trial , error, found key change if application pool identity changes. 2 sites have same keys because running under network service credential. once change application pool identity of 1 site, begin have different validation/encryption keys.

however, after deploy 2 sites server, same machine keys after changing application pool identity. 2 servers have same hardware , software configuration.

i know if there reference actual logic of how machine key generated under autogenerate,isolateapps setting. on web, there lot of articles talking setting same machine key in web farm scenario. encountered problem on opposite side. per web application auto key generation not seem work properly. there has same problem before?

do have web.config setting may overriding iis setting? factor in if telling servers use specific keys may that.


Comments

Popular posts from this blog

linux - Using a Cron Job to check if my mod_wsgi / apache server is running and restart -

actionscript 3 - TweenLite does not work with object -

jQuery Ajax Render Fragments OR Whole Page -