...
How can I use the Gateway with my application?
Instructions for using To use the gateway are available in the wiki (link?). Basicially, the application owner must decide which social providers s/he is willing to accept as authentication sources. In addition, the site hosting the application (or the application itself) will likely need a an extensible Discovery Service so that browser users can identify their Home Organization (more detail available here)presumably a member of InCommon) and/or one or more social providers.
There are many different ways that a site could configure an SP to use the Social-to-SAML Gateway. To keep things straightforward and simple, here is a description of one way to do this:
- Deploy and configure a Install the Shibboleth SP component. Documentation available here.Deploy and configure or use an existing deployment.
- Install the Discovery Service component provided by the Shibboleth project. Documentation available herebundled with the SP.
- Make sure the SP is a member of the InCommon Federation, adding it to InCommon metadata if necessary. (This is because the Gateway consumes InCommon metadata.)
- Choose which Social Identity social providers you want to use. (A list is available here.of supported social providers is given on the Social-to-SAML Gateway Demo page.)
- Configure the SP to load metadata for the chosen Social Identity Providers.social providers. (Metadata files are linked on the Social-to-SAML Gateway Demo page.)
- Configure the SP (and possibly the application) to consume Review the attributes provided by the chosen Identity Providers. Ensure that your applications can support long identifier valuessocial providers. (In particular, some social providers assert long, opaque identifiers.)
If you have questions or problems, please post them on the mailing list.
Which social identity providers does the Gateway support?
...