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

FIWARE.Request.Tech.Apps.Store.standard usage of Wstore

    Details

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

      Description

      Francisco PĂ©rez (Integration lead of FIspace project) sent a message using
      the contact form at http://catalogue.fiware.org/.

      Hi,

      just reattempting the standard procedure of usage of Wstore and communication
      channel in order to analize pro/contra's. In FIspace, we use an instance of
      Wstore, from the beginining, installed in our own premises. We have suffered
      incoviences about this approach and benefits. I would like to test the
      standard procude and usage of Wstore in order to know what is the defined
      path in order compare with our current approach.

      One prerequisite is the wstore instance provided should be configure to use
      an specific instance of Keycloak which is oauth 2.0 compatible.

      Do you think the standard approach is feasible with that prerequisities?

      Thanks

      _______________________________________________
      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help-new
      [Created via e-mail received from: paco@limetri.eu]

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        7d 23h 48m 1 Francisco de la Vega 02/Oct/15 11:56 AM
        In Progress In Progress Answered Answered
        52d 4h 8m 1 Francisco de la Vega 23/Nov/15 3:04 PM
        Answered Answered Closed Closed
        1s 1 Francisco de la Vega 23/Nov/15 3:04 PM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        mev Manuel Escriche made changes -
        HD-Enabler WStore [ 10858 ]
        HD-Chapter Apps [ 10836 ]
        mev Manuel Escriche made changes -
        Sender Email paco@limetri.eu
        mev Manuel Escriche made changes -
        Summary FIWARE.Request.Tech.standard usage of Wstore FIWARE.Request.Tech.Apps.Store.standard usage of Wstore
        mev Manuel Escriche made changes -
        Summary [Fiware-tech-help] [Store - WStore] standard usage of Wstore FIWARE.Request.Tech.standard usage of Wstore
        fdelavega Francisco de la Vega made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        fdelavega Francisco de la Vega made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        Hide
        fw.ext.user FW External User added a comment -

        Therefore, we can conclude standard procedures doesnt apply with that
        prerequisite.

        It is a pity, because in Fispace we have already reached this
        integration but to maintain the development evolution of wstore is
        difficult. If you may reconsider this statement, please do not hesite to
        get in contact us.

        Thanks, you can close the issue

        Show
        fw.ext.user FW External User added a comment - Therefore, we can conclude standard procedures doesnt apply with that prerequisite. It is a pity, because in Fispace we have already reached this integration but to maintain the development evolution of wstore is difficult. If you may reconsider this statement, please do not hesite to get in contact us. Thanks, you can close the issue
        Hide
        fdelavega Francisco de la Vega added a comment -

        Hi Francisco,

        Sorry for the delay answering. I dont know if this is still an issue.

        Regarding having an instance of WStore integrated with Keycloak, you have to take into into account that the user API as well as the concepts (roles, organizations, etc) of Keycloak and Keyrock are different, so some development is required (Indeed as far I know this task was already done in FI-Space). So, we are not planning to make specific integration development to accomodate WStore to Keycloak APIs.

        Best regards,
        Francisco

        Show
        fdelavega Francisco de la Vega added a comment - Hi Francisco, Sorry for the delay answering. I dont know if this is still an issue. Regarding having an instance of WStore integrated with Keycloak, you have to take into into account that the user API as well as the concepts (roles, organizations, etc) of Keycloak and Keyrock are different, so some development is required (Indeed as far I know this task was already done in FI-Space). So, we are not planning to make specific integration development to accomodate WStore to Keycloak APIs. Best regards, Francisco
        Hide
        mev Manuel Escriche added a comment -

        Fran, please, what prevents you to answer? - thanks

        Show
        mev Manuel Escriche added a comment - Fran, please, what prevents you to answer? - thanks
        Hide
        fw.ext.user FW External User added a comment -

        Well, our experiences is a bit different.

        However, the question is, due to the fact is not recommended to have our
        own installation and Fiware is encouraging the usage of instances in
        FiLab, the question is,

        if it is possible to request an instance of Wstore linked with our own Idm.

        Thanks

        Show
        fw.ext.user FW External User added a comment - Well, our experiences is a bit different. However, the question is, due to the fact is not recommended to have our own installation and Fiware is encouraging the usage of instances in FiLab, the question is, if it is possible to request an instance of Wstore linked with our own Idm. Thanks
        fdelavega Francisco de la Vega made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        fdelavega Francisco de la Vega added a comment -

        Hi Francisco,

        WStore implements an OAuth2 client, so the authentication process (redirection, and obtaining the access token) can be direcly done just configurng the URL of keycloak an the paths for obtaining the authorization code and the access token.

        Nevertheless, WStore needs to retrieve user information (complete name, organizations and roles). This is done once the OAuth2 process has finished and the access token has been obtained. Note that the API for obtaining user information depends on the concrete IdM implementation being used, and that WStore currently spects the user info structure given by the FIWARE IdM. In this regard in is needed to replace one method that receives the concrete JSON and generates the internal structures.

        Best regads,
        Francisco

        Show
        fdelavega Francisco de la Vega added a comment - Hi Francisco, WStore implements an OAuth2 client, so the authentication process (redirection, and obtaining the access token) can be direcly done just configurng the URL of keycloak an the paths for obtaining the authorization code and the access token. Nevertheless, WStore needs to retrieve user information (complete name, organizations and roles). This is done once the OAuth2 process has finished and the access token has been obtained. Note that the API for obtaining user information depends on the concrete IdM implementation being used, and that WStore currently spects the user info structure given by the FIWARE IdM. In this regard in is needed to replace one method that receives the concrete JSON and generates the internal structures. Best regads, Francisco
        mev Manuel Escriche made changes -
        Assignee Francisco de la Vega [ fdelavega ]
        mev Manuel Escriche made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        fw.ext.user FW External User created issue -

          People

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

            Dates

            • Created:
              Updated:
              Resolved: