2nd factor IdP AuthN conditional on user attribute

Stefan Wold ratler at stderr.eu
Thu Feb 9 17:14:50 EST 2017


The framework really doesn't dictate how you do your part. It's for letting
everybody *else* control how U2F is combined with other methods and when
it's triggered, so you don't have to think about any of that. You just do
U2F by itself, and you're done. If that's what your flow does now, you're
probably 90% done.


Alright, thanks. I'll read up on the framework to get a better
understanding of it. Hopefully there's just a few tweaks necessary to have
everything working with 3.3 then.


I don't really disagree, but the problem is our competitors *do* handle
that role, so for us to not include that functionality means we're not
providing a comparable feature and we're not giving people something they
can really deploy.

Of course, I'm open to partnering on that piece, but it needs to be
something open source and robust enough that we can clearly say "use that".


Ok, that makes sense. Without promising too much I believe there could be
an opportunity to actually partner up and build an open source solution
that handles token management. What's the time frame for the release of 3.4?

/Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170209/aaf3f66f/attachment.html>


More information about the users mailing list