If your business case allows for the 2 factor authentication to happen at the time of user sign in, you may be able to use a User Sign In Event Handler to process the code and either allow the authentication to happen or not. To achieve the single session requirement, you'd set AllowPersistentLoginCookie to false in Web.config/User.config.

If you have to do this only on a single page, while still allowing for separate "regular" site authentication, I'm not sure how that would be accomplished without forking the code.

Jamie

You may be able to do this with a pair of custom features. Put the first feature on the "landing" page, where you prompt for the key. Once the key is validated, set your own session cookie and redirect to the form page, which hosts your second feature and the Form Wizard Pro instance. The second feature would check the session key for validity, and if that fails, redirect to the "not authorized" page.

I hope that helps,

Jamie

I'd recommend reading through Developer Docs,  checking out the quick start, and the training videos. If you've already worked with Visual Studio and C#, then it'll be a pretty short learning curve to get started working on mojoPortal features. Once you get the hang of it, it's really not very difficult. As Joe Audette always says, the code is the greatest teacher, and it's all out there for you to examine and search.

If you still think it's beyond what you want to tackle, I know that some of the advertisers right here on mojoPortal.com will do custom development work.

I hope that helps,

Jamie