[Backlogmanager] [FIWARE-JIRA] (HELP-14146) [fiware-stackoverflow] Fiware pep-proxy and idm communication issue

[Fernando Lopez (JIRA)]

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

Fernando Lopez updated HELP-14146:
----------------------------------
    Description: 
Created question in FIWARE Q/A platform on 17-05-2018 at 18:05
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/50396043/fiware-pep-proxy-and-idm-communication-issue


+Question:+
Fiware pep-proxy and idm communication issue

+Description:+
I wanted to connect pep-proxy with the idm .. so I followed the installation of pep from that link ..
https://github.com/ging/fiware-pep-proxy by building it from the source .
That was the config file i was supposed to edit 

// Credentials obtained when registering PEP Proxy in app_id in Account Portal
config.pep = {
    app_id: '',
    username: '',
    password: '',
    trusted_apps : []
}


i also wanted to know how could i get both the app_id  and the trusted_apps parameters and i'm also confused with the meaning of the app_id whether it's the client id or not . 

That was the first part of my issue.

when i put the client id with app id and put the username and password of pep proxy that i got when i registerd it on idm ,
i got keystone communication error

when i edited the idm host parameter by adding "http" at the beginning , i got no token and i get "token undefined" message .
Also when i edited the username and password by putting those of idm account  , everytime i get a new token.
So i wanted to know the best way to build the fiware pep-proxy and make it communicate correctly with the idm with no problems . 

Then i tried to follow the installation commands from the docker file . On building the pep-proxy with these commands , i got a new config file which is that of fiware academia 



this config file is different from the first one i worked on . When i followed the steps in this video https://www.youtube.com/watch?v=dtKsjGbJ7Xc&index=10&list=PLARS-yIy9nOoBIOJS05Rpkvu1pZiNTgPT  and configured the username and password by putting those of the pep-proxy , i got this error.



On putting "http" before keystone parameter as follows 

config.keystone_host = 'http://cloud.lab.fiware.org';

i got this message



But on putting the username and password of idm in the configuration as shown below 
config.username = 'idm_user_mail;
config.password = 'password';

i always get a new token .

Now , I want to know the best way to get the pep-proxy and the idm work together as i'm still struggling to make them communicate properly.


  was:

Created question in FIWARE Q/A platform on 17-05-2018 at 18:05
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/50396043/fiware-pep-proxy-and-idm-communication-issue


+Question:+
Fiware pep-proxy and idm communication issue

+Description:+
I wanted to connect pep-proxy with the idm .. so I followed the installation of pep from that link ..
https://github.com/ging/fiware-pep-proxy by building it from the source .
That was the config file i was supposed to edit 

// Credentials obtained when registering PEP Proxy in app_id in Account Portal
config.pep = {
    app_id: '',
    username: '',
    password: '',
    trusted_apps : []
}


i also wanted to know how could i get both the app_id  and the trusted_apps parameters and i'm also confused with the meaning of the app_id whether it's the client id or not . 

That was the first part of my issue.

when i put the client id with app id and put the username and password of pep proxy that i got when i registerd it on idm ,
i got keystone communication error

when i edited the idm host parameter by adding "http" at the beginning , i got no token and i get "token undefined" message .
Also when i edited the username and password by putting those of idm account  , everytime i get a new token.
So i wanted to know the best way to build the fiware pep-proxy and make it communicate correctly with the idm with no problems . 

Then i tried to follow the installation commands from the docker file . On building the pep-proxy with these commands , i got a new config file which is that of fiware academia 



this config file is different from the first one i worked on . When i followed the steps in this video https://www.youtube.com/watch?v=dtKsjGbJ7Xc&index=10&list=PLARS-yIy9nOoBIOJS05Rpkvu1pZiNTgPT  and configured the username and password by putting those of the pep-proxy , i got this error.



On putting "http" before keystone parameter as follows 

config.keystone_host = 'http://cloud.lab.fiware.org';

i got this message



But on putting the username and password of idm in the configuration as shown below 
config.username = 'idm_user_mail;
config.password = 'password';

i always get a new token .

Now , I want to know the best way to get the pep-proxy and the idm work together as i'm still struggling to make them communicate properly.


     HD-Enabler: Wilma

> [fiware-stackoverflow] Fiware pep-proxy and idm communication issue
> -------------------------------------------------------------------
>
>                 Key: HELP-14146
>                 URL: https://jira.fiware.org/browse/HELP-14146
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Alvaro Alonso
>              Labels: fiware, fiware-wilma, keystone, security
>
> Created question in FIWARE Q/A platform on 17-05-2018 at 18:05
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/50396043/fiware-pep-proxy-and-idm-communication-issue
> +Question:+
> Fiware pep-proxy and idm communication issue
> +Description:+
> I wanted to connect pep-proxy with the idm .. so I followed the installation of pep from that link ..
> https://github.com/ging/fiware-pep-proxy by building it from the source .
> That was the config file i was supposed to edit 
> // Credentials obtained when registering PEP Proxy in app_id in Account Portal
> config.pep = {
>     app_id: '',
>     username: '',
>     password: '',
>     trusted_apps : []
> }
> i also wanted to know how could i get both the app_id  and the trusted_apps parameters and i'm also confused with the meaning of the app_id whether it's the client id or not . 
> That was the first part of my issue.
> when i put the client id with app id and put the username and password of pep proxy that i got when i registerd it on idm ,
> i got keystone communication error
> when i edited the idm host parameter by adding "http" at the beginning , i got no token and i get "token undefined" message .
> Also when i edited the username and password by putting those of idm account  , everytime i get a new token.
> So i wanted to know the best way to build the fiware pep-proxy and make it communicate correctly with the idm with no problems . 
> Then i tried to follow the installation commands from the docker file . On building the pep-proxy with these commands , i got a new config file which is that of fiware academia 
> this config file is different from the first one i worked on . When i followed the steps in this video https://www.youtube.com/watch?v=dtKsjGbJ7Xc&index=10&list=PLARS-yIy9nOoBIOJS05Rpkvu1pZiNTgPT  and configured the username and password by putting those of the pep-proxy , i got this error.
> On putting "http" before keystone parameter as follows 
> config.keystone_host = 'http://cloud.lab.fiware.org';
> i got this message
> But on putting the username and password of idm in the configuration as shown below 
> config.username = 'idm_user_mail;
> config.password = 'password';
> i always get a new token .
> Now , I want to know the best way to get the pep-proxy and the idm work together as i'm still struggling to make them communicate properly.



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