advocacy tips

[Charlton Rose]

My company has several multi-tenant SaaS products and is looking for a
good, customer-facing SSO solution.  At present, we're expending a lot of
energy examining IDaaS providers (OneLogin, Ping, etc.) – some of them
quite costly – and I've been trying to generate some interest in
Shibboleth.  However, I'm dealing with some "perception" problems that I'd
like some help getting through.  The primary perception problem is that
because it's free to use, it's not going to be as capable, robust,
flexible, or as easy to use as something we can pay for.

Yes, I know, it's a typical problem one runs into when trying to sell open
source to a non-technical decision maker.  I'm not asking for those kinds
of general arguments, but rather, arguments about IDP/SSO implementation.

I assume a few users on this list had the option to *not* choose
Shibboleth, did so anyway, and are now glad they did.  Can anyone offer
some tips on how to present Shibboleth as a more attractive option, or
explain to me why they're glad they chose Shibboleth over some of the
well-known IDaaS providers?  Contrary testimonials are also welcome, I
suppose.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161130/8fa3ec55/attachment.html>