...
To report issues or bugs, suggest additional features, or to outline your use case, fill out the Social-to-SAML Feedback Form. Use case descriptions will be used as input to the pilot assessment.
Using the Gateway
What would using this
...
Gateway look like to browser users ?
There is a set of demo sites available here. The entry for each of the supported social providers includes a clickable link to demonstrate the user experience.
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:
- Install the Shibboleth SP or use an existing deployment.
- Install the Discovery Service component bundled 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 providers you want to use. (A list of supported social providers is given on the Social-to-SAML Gateway Demo page.)
- Configure the SP to load metadata for the chosen social providers. (Metadata files are linked on the Social-to-SAML Gateway Demo page.)
- Configure the SP (and possibly the application) to consume the attributes provided by the chosen social 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?
...