Alternatives to DS deployment

[Eric Goodman]

Was just looking at the instructions for installing the Discovery Service (https://wiki.shibboleth.net/confluence/display/SHIB2/DSInstall) and it says the following:

"The first question you should ask is whether you need to install the DiscoveryService<https://wiki.shibboleth.net/confluence/display/SHIB2/DiscoveryService>. If you're working in a non-Java environment, you may find it easier to build a selection page in a more native fashion, or you may find that the SP alone provides enough rudimentary support to get started."

I'm not sure I'm fully grokking the advice here. Are these the kinds of alternatives being suggested? Are there other common modes to consider? Or is something else implied here?

* link to an existing WAYF/DS (such as InCommon's WAYF/Discovery Service) rather than deploying locally
* present a static list of idp-initiated SSO links
* present a static list of IdPs, then initiate actual authentication requests by calling SAML libraries and redirecting the user directly in your app (instead of having the SP do this)

Thanks,

--- Eric


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130618/1f981c92/attachment-0001.html