Spring Social
  1. Spring Social
  2. SOCIAL-344

Support for sending additional provider-specific parameters at request-token time.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      In order to support certain provider-specific features (e.g., scope with LinkedIn), it is necessary to pass additional non-standard parameters at the time the request token is fetched. Spring Social should support the ability to send such parameters.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Craig Walls
            Reporter:
            Craig Walls
          • Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: