Spring Security OAuth
  1. Spring Security OAuth
  2. SECOAUTH-209

Facebook sample in tonr2 doesn't work because token cannot be parsed

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: 1.0.0.M6
    • Fix Version/s: 1.0.0.RC1
    • Component/s: OAuth 2
    • Labels:
      None

      Description

      Facebook sample in tonr2 doesn't work because token cannot be parsed. Facebook unaccountably is sending the token form encoded, despite being explicitly asked to send it in application/json. I don't really know what to make of that, and it's not clear that we should support that kind of thing in Spring Security OAuth (Spring Social seems like a better place).

        Activity

        Hide
        Dave Syer added a comment -

        FormOAuth2AccessTokenMessageConverter has always covered the form-encoded case. The problem is that Facebook has started sending the content type as text/plain. I've added that as a supported media type so the demo works again, but there has to be a limit to this (Spring Social is a better place for weird third party client support).

        Show
        Dave Syer added a comment - FormOAuth2AccessTokenMessageConverter has always covered the form-encoded case. The problem is that Facebook has started sending the content type as text/plain. I've added that as a supported media type so the demo works again, but there has to be a limit to this (Spring Social is a better place for weird third party client support).

          People

          • Assignee:
            Dave Syer
            Reporter:
            Dave Syer
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: