Forum Discussion
2nd Factor of Authentication for documents within Sharepoint
The short answer is that this is not an easy thing to do. The APM access policy only evaluates once at the beginning of the session, so to cause any sort of re-validation, you essentially have to dump the existing session and start a new one. The new ACCESS::policy evaluate command would technically allow you to do some post-policy processing, but only does so in clientless-mode, so no opportunity to display a logon page.
There are, potentially, two other options:
-
Use LTM and iRules to generate an RSA token logon page (not an APM logon page), then submit that data via ACCESS::policy evaluate. I haven't tested this idea, but it should work.
-
There is a technique that allows you to store relevant information from the current session into a short-lived session table entry, delete the old session, start a new one, and then dump the old data into the new access session. Not the most intuitive thing in the world, but certainly an option.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com