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

FIWARE.Request.Tech.Security.IDM-KeyRock.Problemwithoauth

    Details

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

      Description

      Dear All,

      I am facing a problem setting oauth security on a context broker node.

      I tried to follow the tutorial but still no luck.
      https://github.com/ging/oauth2-example-client/blob/master/docs/oauth2_tutorial.pdf

      According to the example the server.js is working and running on port 3000
      (I changed it because I can't have apache2 and oauth listening on the same
      port 80), attached print screen.
      Our context broker instance is running here and you can check the version
      http://194.177.207.101:1026/version
      Also apache web server is running :
      http://194.177.207.101/

      I created an account on FI Lab application and generated client id and
      secret. attached print screen also. and edited the config and server file.
      attached both of them.

      Now I keep trying to do get https://194.177.207.101:3000 but no response.

      So what I am doing wrong here, what is the missing part, should I edit the
      redirect part in the server.js file ?

      Best,,
      Ahmed Sadek

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

      [Created via e-mail received from: Ahmed Sadek <don1559@gmail.com>]

      1. config.js
        0.3 kB
        FW External User
      2. oauth
        2 kB
        FW External User
      3. server.js
        3 kB
        FW External User
      1. Screenshot from 2015-03-28 17_50_07.png
        153 kB
      2. Screenshot from 2015-03-28 17_52_05.png
        185 kB

        Activity

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

        Renamed attached file: 'Screenshot from 2015-03-28 17:52:05.png' to 'Screenshot from 2015-03-28 17_52_05.png' because it contained invalid character(s).

        Show
        fw.ext.user FW External User added a comment - Renamed attached file: 'Screenshot from 2015-03-28 17:52:05.png' to 'Screenshot from 2015-03-28 17_52_05.png' because it contained invalid character(s).
        Hide
        fw.ext.user FW External User added a comment -

        Renamed attached file: 'Screenshot from 2015-03-28 17:50:07.png' to 'Screenshot from 2015-03-28 17_50_07.png' because it contained invalid character(s).

        Show
        fw.ext.user FW External User added a comment - Renamed attached file: 'Screenshot from 2015-03-28 17:50:07.png' to 'Screenshot from 2015-03-28 17_50_07.png' because it contained invalid character(s).
        Hide
        cdangerville Cyril Dangerville added a comment -

        This issue relates to the IdM GE's OAuth interface, so reassigning to the IDM GE owner (Alvaro Alonso).

        Show
        cdangerville Cyril Dangerville added a comment - This issue relates to the IdM GE's OAuth interface, so reassigning to the IDM GE owner (Alvaro Alonso).

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: