Configuring Orion Context Broker, Wilma PEP Proxy and Keyrock IdM

Question

My name is Joe and I'm in traineeship about IoT security and Identity Management. In order to develop some solutions to a project I've been assigned, I have to configure and integrate Orion, Wilma and Keyrock (and potentially a PDP, but that comes later). I've found some tutorials and FIWARE official guides, but I'm seriously in trouble with the configuration. I've already learned the "theory" behind: I'm aware of the FIWARE security architecture but the problem is on practice. As a first approach to the problem, I thought that trying to get the token with a token request could be a good way to start, as follows:

curl -X POST --data "grant_type=password&username=user&password=pwd” http://192.168.100.241:5000/oauth2/token --header "'Host':'192.168.100.241','Content-Type':'application/x-www-form-urlencoded','Authorization':'Basic base64(client_id+":"+client_secret)'"

where 192.168.100.241 is the IP address of the host where Keystone runs. The response to this is the following:

{ "error": { "message": "Impossibile trovare la risorsa.", "code": 404, "title": "Not Found" } }

Now, how this problems can be solved? Perhaps I'm missing something or probably I'm unaware of something. And later, how can the PEP Proxy enforce some policies on Orion requests (or receive them directly and later, if allowed, communicate them to Orion)? Could you help me? I'm terribly in trouble.
Thank you :-)

Answer 1

You can see how to integrate Orion Context Broker, Keyrock IdM and Wilma PEP Proxy in the following link:

https://www.slideshare.net/daltoncezane/integrating-fiware-orion-keyrock-and-wilma

I already had these doubts like you. I hope it helps.

Include client_id and secret_id in the grant_type :

grant_type=password&username=${_user}&password=${_pass}&client_id=${CLIENT_ID}&client_secret=${CLIENT_SECRET}