[Backlogmanager] [FIWARE-JIRA] (HELP-13963) [fiware-stackoverflow] FIWARE PEP 6.2 can' t get a ' x-subject-token' when staring it

[Alvaro Alonso (JIRA)]

     [ https://jira.fiware.org/browse/HELP-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alvaro Alonso updated HELP-13963:
---------------------------------
    Status: In Progress  (was: Open)

> [fiware-stackoverflow] FIWARE PEP 6.2 can't get a 'x-subject-token' when staring it
> -----------------------------------------------------------------------------------------------
>
>                 Key: HELP-13963
>                 URL: https://jira.fiware.org/browse/HELP-13963
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Alvaro Alonso
>              Labels: fiware, fiware-orion, fiware-wilma
>
> 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-6-2-cant-get-a-x-subject-token-when-staring-it
> +Question:+
> FIWARE PEP 6.2 can't get a 'x-subject-token' when staring it
> +Description:+
> I try to protect orion with PEP 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 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.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)