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

FIWARE.Request.Tech.Apps.Store.AccessTokenProblem

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-TECH-HELP
        • Labels:
          None

          Description

          Elias Kanakis sent a message using the contact form at
          http://catalogue.fiware.org/.

          Dear Francisco de la Vega,

          Our team participates in the FI-ADOPT call with the project QualiFI.

          We are trying to integrate the public instance of WStore GE
          (https://store.lab.fiware.org) in our application in order to register and
          publish offerings on it using the supported APIs
          (http://conwetlab.github.io/wstore/#action_publish-an-offering_examples).

          However, we deal a problem with the token (Authorization: Bearer
          YOUR_OAUTH2_TOKEN) that the API needs.

          We have tested the API
          POST http://cloud.lab.fiware.org:4730/v2.0/tokens
          {
          "auth": {
          "passwordCredentials":

          { "username": "my-fiware-email", "password": "my-fiware-password" }

          }
          }
          but without success.

          Could you help us how to obtain the Bearer token to use the APIs?

          Thank you and happy new year,
          Elias Kanakis

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-tech-help mailing list
          Fiware-tech-help@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-tech-help

          [Created via e-mail received from: optimum.euprojects@gmail.com]

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            fdelavega Francisco de la Vega added a comment -

            Dear Elias,

            The mechanism you are using returns a KeyStone token, so it can be used to access the cloud APIs and the platform itself. This token is of a lower level of the one you required.

            You can check that by accessing:

            https://account.lab.fiware.org/user?access_token=RETURNED_TOKEN

            If you try this URL with the token returned by that request you will see that it tells you that the token is not valid.

            What you require is a Bearer token for IdM applications. You can obtain this access token by following the OAuth2 process using your app info in the account endpoints

            https://account.lab.fiware.org/oauth2/code
            https://account.lab.fiware.org/oauth2/token

            Best regards,
            Francisco

            Show
            fdelavega Francisco de la Vega added a comment - Dear Elias, The mechanism you are using returns a KeyStone token, so it can be used to access the cloud APIs and the platform itself. This token is of a lower level of the one you required. You can check that by accessing: https://account.lab.fiware.org/user?access_token=RETURNED_TOKEN If you try this URL with the token returned by that request you will see that it tells you that the token is not valid. What you require is a Bearer token for IdM applications. You can obtain this access token by following the OAuth2 process using your app info in the account endpoints https://account.lab.fiware.org/oauth2/code https://account.lab.fiware.org/oauth2/token Best regards, Francisco
            Hide
            Permalink
            fdelavega Francisco de la Vega added a comment -

            I didn't received any feedback from the issuer, so I will proceed to close the issue and reopen it if necessary

            Show
            fdelavega Francisco de la Vega added a comment - I didn't received any feedback from the issuer, so I will proceed to close the issue and reopen it if necessary

              People

              • Assignee:
                fdelavega Francisco de la Vega
                Reporter:
                fw.ext.user FW External User
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: