As I understand it (which may be wrong) your application redirects to a SAML provider to authenticate, so that if you've already logged in it knows this and forwards you straight back to your application.
But it's the SAML provider that handles authentication, so however that works - two factor, fingerprint, bum scan* etc it handles it.
Is that right?
* Monsters vs Aliens film
That is basically right.
Is it specifically SAML you are looking at or just general token based single sign in type stuff?
Cloud version of our product supports SAML. Client have asked for single sign-on, but also for multi-factor authentication. But if *their* SAML provider supports multi-factor athentication, we still don't have to do anything other than integrate with SAML just the same... I think.
STW - best forum ever.
In a previous life before I thought that that running a bike company might be a good idea, I was a programmer and authentication was one of my specialist areas. I'd managed to expunge all thoughts of SAML from my brain until reading this post. All I can say is that thinking back to those heady days of SSO has reminded me what a great decision starting a bike company actually was!
You have to find your inner geek to do this job.