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

[fiware-stackoverflow] Not able to Login in keyrock IDM using Nginx

    Details

      Description

      Created question in FIWARE Q/A platform on 09-04-2019 at 15:04
      Please, ANSWER this question AT https://stackoverflow.com/questions/55594461/not-able-to-login-in-keyrock-idm-using-nginx

      Question:
      Not able to Login in keyrock IDM using Nginx

      Description:
      I have installed nginx reverse proxy server and fiware keyrock IDM. I want to access fiware keyrock using Nginx server with the url https://"nginx-ip"/key

      My nginx conf is as follows:

      location /idm/

      { proxy_set_header X-Forwarded-Host $host; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; rewrite ^/idm(/.*)$ $1 break; proxy_pass https://172.30.66.235:3443; proxy_redirect / /idm/; sub_filter '="/' '="/idm/'; sub_filter '= "/' '= "/idm/'; sub_filter '=\'/' '=\'/idm/'; sub_filter_once off; }

      After configuring the nginx configuration, I am able to load/access keyrock at:
      https://nginx-ip/idm.

      But when I try to login it doesn't logins and shows the same homepage of keyrock IDM. I have actually done several changes at nginx end but none of it worked.

      Fiware IDM : https://github.com/ging/fiware-idm/tree/7.5.1

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2019-04-09 18:06|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2019-04-09 18:06|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: