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

FIWARE.Question.Tech.FIWARE - PEP Proxy configured to HTTPS.

    Details

      Description

      Created question in FIWARE Q/A platform on 17-01-2017 at 06:01
      Please, ANSWER this question AT http://stackoverflow.com/questions/41689745/fiware-pep-proxy-configured-to-https

      Question:
      FIWARE - PEP Proxy configured to HTTPS

      Description:
      I would like to know how I configure the PEP Proxy so that I can exchange messages through HTTPS. I have an instance of Orion context broker that is accessed only after pass by the PEP Proxy. My PEP Proxy (Wilma) configuration file (config.js) has the following:

      config.app_host = 'my_orion_ip'; //change to your Orion address
      config.app_port = '1026'; //change to your Orion port

      config.username = 'pep_proxy_credential_obtained_at_portal';
      config.password = 'password_obtained_at_portal';

      I have also HTTPS to HTTP (Nginx configured as reverse proxy) so that my requests directly sent to Orion are secure. The HTTPS is working only without PEP Proxy flow. When I insert the authorization/authentication flow, I am facing problems, because the PEP Proxy does not handle with the SSL certificate.

      I want to integrate what I have in a way I can communicate with Orion only by HTTPS, including the PEP Proxy flow. I've searched but I did not find nothing useful related to HTTPS configuration in PEP Proxy.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2017-01-17 09:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-01-17 09:05|CREATED monitor | # answers= 0, accepted answer= False

          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: