I am putting together a site for someone which is internal Windows Integrated Security. We need to make sure that before they user an application that they have filled in a user profile.
OK, well I could make sure on session start that they do have one and if not redirect them to the relevent page, the issue is that once the session has started there is nothing to stop them re-trying the link and getting to the desired URL having abandonded the profile page.
I want a mechanism to ensure that they do not have access unless they have done this.
Thoughts so far . . . .
1.) Mix windows authentication with forms authentication ( Messy especially with timeouts )
2.)Put code in the page load of my master pages to test that there user object has a property which tells me they have a profile.
3.) Make every page inherit a class which tests this.
I dont really like any of the above. Does anyone have a cleaner so ...
Go to the complete details ...