Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Enabler:Wilma
Description
Created question in FIWARE Q/A platform on 17-05-2018 at 18:05
Please, ANSWER this question AT 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 =
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.
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
Assignee | Alvaro Alonso [ aalonsog ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
HD-Enabler | Wilma [ 10890 ] | |
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. |
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. |
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
19d 12h 27m | 1 | Alvaro Alonso | 06/Jun/18 9:33 AM | |||||
|
1s | 1 | Alvaro Alonso | 06/Jun/18 9:33 AM | |||||
|
1s | 1 | Alvaro Alonso | 06/Jun/18 9:33 AM |
2018-05-17 21:05|CREATED monitor | # answers= 0, accepted answer= False