Uploaded image for project: 'Help-Coaches-Desk'
  1. Help-Coaches-Desk
  2. HELC-853

FIWARE.Request.Coach.FINODEX.Problems with PEP Proxy and Orion Context Broker

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: FINODEX
    • Labels:
      None

      Description

      Hi Finodex Fiware team,

      We meet last week in Trento, and I told you some issues we had while
      implementing PEP Proxy + Orion Context Broker.
      The main problem we are having was that we want to subscribe an user to
      changes in a sensor value that is stored in Orion. To secure the access, we
      included a security module composed by PEP Proxy (Wilma), IdM (Keyrock) and
      Authorization PDP (AuthZForce). We are able to query context and receive
      the value in the user side, but we are not able to make the changes get to
      the users when they are not requesting them directly.
      In Orion Context Broker, there is an option to subscribe to different
      events. We are able to subscribe the user but, when there is a change and
      Orion tries to notify the user, this notification dies in the PEP Proxy. We
      tried contacting Alvaro Alonso (aalonsog@dit.upm.es), which is the Wilma
      PEP Proxy developer, and he told us that PEP Proxy is only able to create
      connections in one direction, meaning that if the user starts the
      communication, the answers will be able to get the user, but it is not
      possible to do it in case the one that starts the communication is Orion.
      We are thinking about sending queries periodically to Orion to check if
      there was any alert, but we are not sure if you have any suggestion for us,
      because we are a little bit lost here.

      Best regards

      Carlos Corrales
      Cofounder Secmotic Innovation S.L.
      http://www.secmotic.com

      _______________________________________________
      Fiware-finodex-coaching mailing list
      Fiware-finodex-coaching@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-finodex-coaching

      [Created via e-mail received from: Carlos Corrales <carlos@secmotic.com>]

        Issue Links

          Activity

          Hide
          fw.ext.user FW External User added a comment -

          Hi all,
          Carlos has this problem in this project.
          could you suggest some things?

          Thank you in advance,
          Pasquale

          Il 01/07/2015 10:25, Carlos Corrales ha scritto:
          > Hi Finodex Fiware team,
          >
          > We meet last week in Trento, and I told you some issues we had while
          > implementing PEP Proxy + Orion Context Broker.
          > The main problem we are having was that we want to subscribe an user
          > to changes in a sensor value that is stored in Orion. To secure the
          > access, we included a security module composed by PEP Proxy (Wilma),
          > IdM (Keyrock) and Authorization PDP (AuthZForce). We are able to query
          > context and receive the value in the user side, but we are not able to
          > make the changes get to the users when they are not requesting them
          > directly.
          > In Orion Context Broker, there is an option to subscribe to different
          > events. We are able to subscribe the user but, when there is a change
          > and Orion tries to notify the user, this notification dies in the PEP
          > Proxy. We tried contacting Alvaro Alonso (aalonsog@dit.upm.es
          > <aalonsog@dit.upm.es>), which is the Wilma PEP Proxy developer,
          > and he told us that PEP Proxy is only able to create connections in
          > one direction, meaning that if the user starts the communication, the
          > answers will be able to get the user, but it is not possible to do it
          > in case the one that starts the communication is Orion. We are
          > thinking about sending queries periodically to Orion to check if there
          > was any alert, but we are not sure if you have any suggestion for us,
          > because we are a little bit lost here.
          >
          > Best regards
          > –
          > Carlos Corrales
          > Cofounder Secmotic Innovation S.L.
          > http://www.secmotic.com
          >
          >
          >
          > _______________________________________________
          > Fiware-finodex-coaching mailing list
          > Fiware-finodex-coaching@lists.fi-ware.org
          > https://lists.fi-ware.org/listinfo/fiware-finodex-coaching

          _______________________________________________
          Fiware-finodex-coaching mailing list
          Fiware-finodex-coaching@lists.fi-ware.org
          https://lists.fi-ware.org/listinfo/fiware-finodex-coaching

          Show
          fw.ext.user FW External User added a comment - Hi all, Carlos has this problem in this project. could you suggest some things? Thank you in advance, Pasquale Il 01/07/2015 10:25, Carlos Corrales ha scritto: > Hi Finodex Fiware team, > > We meet last week in Trento, and I told you some issues we had while > implementing PEP Proxy + Orion Context Broker. > The main problem we are having was that we want to subscribe an user > to changes in a sensor value that is stored in Orion. To secure the > access, we included a security module composed by PEP Proxy (Wilma), > IdM (Keyrock) and Authorization PDP (AuthZForce). We are able to query > context and receive the value in the user side, but we are not able to > make the changes get to the users when they are not requesting them > directly. > In Orion Context Broker, there is an option to subscribe to different > events. We are able to subscribe the user but, when there is a change > and Orion tries to notify the user, this notification dies in the PEP > Proxy. We tried contacting Alvaro Alonso (aalonsog@dit.upm.es > < aalonsog@dit.upm.es >), which is the Wilma PEP Proxy developer, > and he told us that PEP Proxy is only able to create connections in > one direction, meaning that if the user starts the communication, the > answers will be able to get the user, but it is not possible to do it > in case the one that starts the communication is Orion. We are > thinking about sending queries periodically to Orion to check if there > was any alert, but we are not sure if you have any suggestion for us, > because we are a little bit lost here. > > Best regards > – > Carlos Corrales > Cofounder Secmotic Innovation S.L. > http://www.secmotic.com > > > > _______________________________________________ > Fiware-finodex-coaching mailing list > Fiware-finodex-coaching@lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-finodex-coaching _______________________________________________ Fiware-finodex-coaching mailing list Fiware-finodex-coaching@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-finodex-coaching
          Hide
          fermin Fermín Galán added a comment -

          User has been answered in his native language. Furhter interaction will happend by email. Closing.

          Show
          fermin Fermín Galán added a comment - User has been answered in his native language. Furhter interaction will happend by email. Closing.

            People

            • Assignee:
              pasquale.vitale Pasquale Vitale
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: