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

FIWARE.Question.Tech.FIWARE PEP Wilma 6.2 can't get a 'x-subject-token' when staring it.

    Details

      Description

      Created question in FIWARE Q/A platform on 12-04-2018 at 04:04
      Please, ANSWER this question AT https://stackoverflow.com/questions/49786857/fiware-pep-wilma-6-2-cant-get-a-x-subject-token-when-staring-it

      Question:
      FIWARE PEP Wilma 6.2 can't get a 'x-subject-token' when staring it

      Description:
      I try to protect orion with PEP Wilma 6.2. Although PEP proxy starts, It can't get a 'x-subject-token'. Why can't PEP get it? Is my configuration incorrect or insufficient?

      PEP Proxy Wilma 6.2
      server.js:70

      IDM.authenticate (function (token)

      { log.info('Success authenticating PEP proxy. Proxy Auth-token: ', token); }

      , function (status, e) {

      lib/idm.js:22
      var authenticate = function(callback, callbackError) {

      var options = {
      host: config.idm.host,
      port: config.idm.port,
      path: '/v3/auth/tokens',
      method: 'POST',
      headers:

      {'Content-Type': 'application/json'}

      };

      .............................................

      log.info(options); // debug
      log.info(protocol); // debug
      log.info(body.auth.identity.password.user); //debug
      proxy.sendData(protocol, options, JSON.stringify(body), undefined, function (status, resp, headers)

      { my_token = headers['x-subject-token']; log.info("my_token:", my_token); //debug callback(my_token); }

      , callbackError);

      Log :
      'my_token' is undefiend.

      pep | 2018-04-12 10:27:44.665 - INFO: Server - Starting PEP proxy in port 80. IdM authentication ...
      pep | 2018-04-12 10:27:44.667 - INFO: IDM-Client - { host: 'account.lab.fiware.org',
      pep | port: 5000,
      pep | path: '/v3/auth/tokens',
      pep | method: 'POST',
      pep | headers:

      { 'Content-Type': 'application/json' }

      }
      pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client - http
      pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client -

      { name: 'pep_proxy_132e42370ad546a8b85d21dd7453b4ae', pep | password: '9077ddf99863487296a75f1ef8fef297' }

      pep | 2018-04-12 10:27:45.723 - INFO: IDM-Client - my_token: undefined
      pep | 2018-04-12 10:27:45.723 - INFO: Server - Success authenticating PEP proxy. Proxy Auth-token: undefined

      Thank you in advance.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        10d 11h 49m 1 Alvaro Alonso 23/Apr/18 2:55 PM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        veronika Veronika Vlnkova made changes -
        HD-Enabler Wilma [ 10890 ]
        Description
        Created question in FIWARE Q/A platform on 12-04-2018 at 04:04
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/49786857/fiware-pep-wilma-6-2-cant-get-a-x-subject-token-when-staring-it


        +Question:+
        FIWARE PEP Wilma 6.2 can't get a 'x-subject-token' when staring it

        +Description:+
        I try to protect orion with PEP Wilma 6.2. Although PEP proxy starts, It can't get a 'x-subject-token'. Why can't PEP get it? Is my configuration incorrect or insufficient?

        PEP Proxy Wilma 6.2
        server.js:70

        IDM.authenticate (function (token) {

            log.info('Success authenticating PEP proxy. Proxy Auth-token: ', token);

        }, function (status, e) {

        lib/idm.js:22
            var authenticate = function(callback, callbackError) {

                var options = {
                    host: config.idm.host,
                    port: config.idm.port,
                    path: '/v3/auth/tokens',
                    method: 'POST',
                    headers: {'Content-Type': 'application/json'}
                };

        .............................................

                log.info(options); // debug
                log.info(protocol); // debug
                log.info(body.auth.identity.password.user); //debug
                proxy.sendData(protocol, options, JSON.stringify(body), undefined, function (status, resp, headers) {
                    my_token = headers['x-subject-token'];
                    log.info("my_token:", my_token); //debug
                    callback(my_token);
                }, callbackError);


        Log :
        'my_token' is undefiend.

        pep | 2018-04-12 10:27:44.665 - INFO: Server - Starting PEP proxy in port 80. IdM authentication ...
        pep | 2018-04-12 10:27:44.667 - INFO: IDM-Client - { host: 'account.lab.fiware.org',
        pep | port: 5000,
        pep | path: '/v3/auth/tokens',
        pep | method: 'POST',
        pep | headers: { 'Content-Type': 'application/json' } }
        pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client - http
        pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client - { name: 'pep_proxy_132e42370ad546a8b85d21dd7453b4ae',
        pep | password: '9077ddf99863487296a75f1ef8fef297' }
        pep | 2018-04-12 10:27:45.723 - INFO: IDM-Client - my_token: undefined
        pep | 2018-04-12 10:27:45.723 - INFO: Server - Success authenticating PEP proxy. Proxy Auth-token: undefined


        Thank you in advance.
        Created question in FIWARE Q/A platform on 12-04-2018 at 04:04
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/49786857/fiware-pep-wilma-6-2-cant-get-a-x-subject-token-when-staring-it


        +Question:+
        FIWARE PEP Wilma 6.2 can't get a 'x-subject-token' when staring it

        +Description:+
        I try to protect orion with PEP Wilma 6.2. Although PEP proxy starts, It can't get a 'x-subject-token'. Why can't PEP get it? Is my configuration incorrect or insufficient?

        PEP Proxy Wilma 6.2
        server.js:70

        IDM.authenticate (function (token) {

            log.info('Success authenticating PEP proxy. Proxy Auth-token: ', token);

        }, function (status, e) {

        lib/idm.js:22
            var authenticate = function(callback, callbackError) {

                var options = {
                    host: config.idm.host,
                    port: config.idm.port,
                    path: '/v3/auth/tokens',
                    method: 'POST',
                    headers: {'Content-Type': 'application/json'}
                };

        .............................................

                log.info(options); // debug
                log.info(protocol); // debug
                log.info(body.auth.identity.password.user); //debug
                proxy.sendData(protocol, options, JSON.stringify(body), undefined, function (status, resp, headers) {
                    my_token = headers['x-subject-token'];
                    log.info("my_token:", my_token); //debug
                    callback(my_token);
                }, callbackError);


        Log :
        'my_token' is undefiend.

        pep | 2018-04-12 10:27:44.665 - INFO: Server - Starting PEP proxy in port 80. IdM authentication ...
        pep | 2018-04-12 10:27:44.667 - INFO: IDM-Client - { host: 'account.lab.fiware.org',
        pep | port: 5000,
        pep | path: '/v3/auth/tokens',
        pep | method: 'POST',
        pep | headers: { 'Content-Type': 'application/json' } }
        pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client - http
        pep | 2018-04-12 10:27:44.668 - INFO: IDM-Client - { name: 'pep_proxy_132e42370ad546a8b85d21dd7453b4ae',
        pep | password: '9077ddf99863487296a75f1ef8fef297' }
        pep | 2018-04-12 10:27:45.723 - INFO: IDM-Client - my_token: undefined
        pep | 2018-04-12 10:27:45.723 - INFO: Server - Success authenticating PEP proxy. Proxy Auth-token: undefined


        Thank you in advance.
        backlogmanager Backlog Manager made changes -
        Summary [fiware-stackoverflow] FIWARE PEP Wilma 6.2 can't get a 'x-subject-token' when staring it FIWARE.Question.Tech.FIWARE PEP Wilma 6.2 can't get a 'x-subject-token' when staring it.
        aalonsog Alvaro Alonso made changes -
        Resolution Dismissed [ 10102 ]
        Status Open [ 1 ] Closed [ 6 ]
        Hide
        aalonsog Alvaro Alonso added a comment -

        duplicated HELP-13963

        Show
        aalonsog Alvaro Alonso added a comment - duplicated HELP-13963
        veronika Veronika Vlnkova made changes -
        Assignee Alvaro Alonso [ aalonsog ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2018-04-13 03:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2018-04-13 03:05|CREATED monitor | # answers= 0, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: