Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8766

[fiware-stackoverflow] FIWARE KeyRock access token request error on iOS client implementation

    Details

      Description

      Created question in FIWARE Q/A platform on 23-11-2015 at 16:11
      Please, ANSWER this question AT https://stackoverflow.com/questions/33874292/fiware-keyrock-access-token-request-error-on-ios-client-implementation

      Question:
      FIWARE KeyRock access token request error on iOS client implementation

      Description:
      I'm trying to request a KeyRock access token via iOS OAuth2 implementation.

      In iOS the callback url on OAuth is not a regular http:// url but is something like myapp://oauth/callback. The url for the authorization request is the following:

      https://account.lab.fiware.org/oauth2/authorize/?response_type=code&client_id=123&redirect_uri=myapp://oauth/callback

      After calling the url, I can login on the Fiware account, authorized my app, but instead of being redirected to my callback address myapp://oauth/callback, I always get the following error:

      Error: An error occurred when trying to obtain the authorization code.

      I can't get my access token and I'm stuck on this page:

      If I try to change the callback url, using a normal http:// address, everything works fine but on iOS that kind of url is unusable as callback in OAuth authentication.

      What's wrong?

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        3d 18h 6m 1 Fernando Lopez 26/May/17 9:11 AM
        In Progress In Progress Answered Answered
        2s 1 Fernando Lopez 26/May/17 9:11 AM
        Answered Answered Closed Closed
        23s 1 Fernando Lopez 26/May/17 9:11 AM

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: