tc100years
asked on
How to disable 'private computer' setting that caches the username for ISA FBA authentication form?
ISA 2006 publishing OWA for Exchange 2003.
FBA with AD.
Logon form has 'This is private computer' option. When this option is selected, the username is cached in a cookie on that client for this site. How do you <easily> <gracefully> disable this setting so that usernames can not be cached in cookies?
Is this possible without disabling the option so that users can still select 'this is a private computer' to extend their session time BUT NOT have thier username show up the next time that client device goes to this page?
owascreenshot.bmp
FBA with AD.
Logon form has 'This is private computer' option. When this option is selected, the username is cached in a cookie on that client for this site. How do you <easily> <gracefully> disable this setting so that usernames can not be cached in cookies?
Is this possible without disabling the option so that users can still select 'this is a private computer' to extend their session time BUT NOT have thier username show up the next time that client device goes to this page?
owascreenshot.bmp
ASKER
Thanks for the quick response but this does not address the behavior of the default exchange form that comes with ISA 2006. The ISA 2006 form caches the username in the cookie when Forms Based Authentication is used. ISA 2004 did not do this...
well you could edit the listener , but as far to my experiance with that it doesnt really work.
you can only customize the form which will not be easyer :)
why do you want to change it anyway?
you can only customize the form which will not be easyer :)
why do you want to change it anyway?
ASKER
If a user, that hasn't been properly trained, chooses 'This is a private computer', it retains that setting and then any future visits to that site will populate the username field with the last successfully negotiated userid. For increased security, I'd like to disable that possibility similar to the behavior of ISA 2004 FBA...
Unfortunately they are two different beasts. ISA2004 really only published owa services whereas ISA2006 does the job properly. Is there a real need to bridge the HTTPS through ISA rather than tunnel it straight through to the Exchange box? You could then edit the exchange owa pages instead
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
tc , i see what you mean and I'm afraid I'm not familiar with a solution to this.
would be great to actually control that.
would be great to actually control that.
http://support.microsoft.c