Created question in FIWARE Q/A platform on 11-07-2016 at 13:07
Please, ANSWER this question AT http://stackoverflow.com/questions/38305650/fiware-wilma-pep-proxy-authorization-failure

Question:
fiware Wilma PEP Proxy authorization failure

Description:
Hi I am trying to setup the fiware PEP proxy for use with fiware cosmos.

I have installed cosmos and the proxy on my local virtual machines.
I believ I have configured the proxy according to the instructions in the install and config guides included in the git repository.
Currently I am trying to use the the keystone Idm instance within FI-Lab and as far as I can tell I have set up my user, organization and application correctly there. I have a trial account with FI-Lab at the moment.

However when I start up the proxy I get the following messages logged to the console:

2016-07-11 11:04:37.079 - INFO: Server - Starting PEP proxy in port 80. Keystone authentication ...
2016-07-11 11:04:38.124 - INFO: Server - Success authenticating PEP proxy. Proxy Auth-token: undefined

The PEP proxy username and password have been taken from the pep-proxy config of the cosmos application registered with the FI-Lab Idm.

config.app_port = '80'

This port is open in my fire wall and according to netstat only the the pep proxy is listening to it.
In any case since the authentication succeeds but and authorisation token i not returned suggests the port is not an issue, but there is some mismatch between the proxy config and the user/application registration in Fi-Lab.

Could somebody give some pointers on where to look for the mismatch.