Multiple web farms sharing Machinekey

[dgermano]

I need some info to make sure I avoid problems with my webfarms.
Currently I'm running 3 separate sites, each with their own webfarm of
2-3 webservers. All of these sites are using the same backend machine
for SessionState info.

I'm wondering what problems might pop up if I set the MachineKey to the
same value on all of the webservers. I know it is required to do this
within the web farm for each site so that postbacks to alernate
machines work. However I have a feeling that if I set the key the same
across my different sites I might get odd session collisions or
something.

Can anybody give me a quick rundown of why this would/wouldn't be a
problem?

Thanks.

[Elliot M. Rodriguez]

dgermano wrote:

I need some info to make sure I avoid problems with my webfarms.
Currently I'm running 3 separate sites, each with their own webfarm of
2-3 webservers. All of these sites are using the same backend machine
for SessionState info.

I'm wondering what problems might pop up if I set the MachineKey to the
same value on all of the webservers. I know it is required to do this
within the web farm for each site so that postbacks to alernate
machines work. However I have a feeling that if I set the key the same
across my different sites I might get odd session collisions or
something.

Can anybody give me a quick rundown of why this would/wouldn't be a
problem?

Thanks.

If youre using a single store for session information (read,
ASPSessionState service or SQL Server), then you wont have any issues
with sessions.

InProc, however, may be an issue, since you wont be able to make them
sticky.