Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

Instructions for using 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 Discovery Service so that browser users can identify their Home Organization (more detail available here).

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:

  1. Deploy and configure a Shibboleth SP component. Documentation available here.
  2. Deploy and configure the Discovery Service component provided by the Shibboleth project. Documentation available here.
  3. Make sure the SP is a member of the InCommon Federation, adding it if necessary.
  4. Choose which Social Identity providers you want to use. A list is available here.
  5. Configure the SP to load metadata for the chosen Social Identity Providers.
  6. Review the attributes provided by the chosen Identity Providers. Ensure that your applications can support long identifier values.

Which social identity providers does the Gateway support?

...