Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Security
-
HD-Enabler:Wilma
Description
Hi,I am the system administrator of Upcom company and we have a project
that we must use some enablers of fiware. I installed the PEP-PROXY
enabler with docker but i have a big problem.I have config the config.js
for running in our server but when i run curl --header "X-Auth-Token:
<our token>" http://localhost(our server), we take as an answer <<Error
in IDM communication>>.Can you help me?
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: nikos kapetanakis <nkapetanakis@upcom.eu>]
Activity
Hi, my project is FerTility. I success to solve my problem with
pep-proxy.Now i have an other problem with keyrock.I have installed it
in my server with docker and i want to update cors policies.Can you help
me?Thanks
Hello,
I've forwarded your request to the person in charge of Keyrock.
Please be more clear explaining your issues in order that we can help you.
Regards,
Giuseppe
Hi,
what do you need exactly?
BR
Hi,I solve my problem.It was problem of firewall.Thanks
Now, we have a new problem with oauth2.We have install succesfull
keyrock,WMarket and Pep-proxy with dockers on our server.We set up
pep-proxy to redirect us to WMarket when X-Auth-Token:<> from pep-proxy
when token is valid.In basic authentication we succeed it without a
problem(we do not need this method) but with oauth2 we take these logs
on Pep-proxy.
2016-01-20 15:25:26.278 - INFO: IDM-Client - Token in cache, checking
timestamp...
2016-01-20 15:25:26.278 - INFO: Root - Access-token OK. Redirecting to
app...
Refused to set unsafe header "accept-encoding"
Refused to set unsafe header "cookie"
2016-01-20 15:25:26.285 - ERROR: HTTP-Client - Error: 401
<div class="error-body">Access is denied due to invalid credentials.</div>
Hi,
the token validation has suceded. That response comes from the backend service you are accessing. So it is not related with Wilma or Keyrock.
BR
Hello,
Before to send your request to the Pep Proxy GE owner I have to ask you some questions. Do you have a community account related to your project?
Is the network of your server configured properly (e.g. security groups, floating IPs)?
Regards,
Giuseppe