Created question in FIWARE Q/A platform on 20-08-2015 at 11:08
Please, ANSWER this question AT http://stackoverflow.com/questions/32114520/wilma-pep-proxy-and-keystone-valid-access-token-not-found

Question:
Wilma pep proxy and keystone - valid access token not found

Description:
I have wilma redirecting valid requests to orion but no messages are reaching it as i always get "Access Token not found" from wilma. The account entered in wilma config file is the admin account of keystone.
From openStack API docs i request tokens using below request.

curl -i \
> -H "Content-Type: application/json" \
> -d '
> { "auth": {
> "identity": {
> "methods": ["password"],
> "password": {
> "user": {
> "name": "userAdmin",
> "domain":

,
> "password": "pw"
> }
> }
> }
> }
> }' \
> http://130.206.115.xxx:5000/v3/auth/tokens ; echo

I think i get a valid token because direct requests to keystone using curl with x-auth-token work fine.

Then i try to curl from my computer

curl --header "X-Auth-Token:$TOKEN" <ipOfWilma>:80/v2/entities

And get as a answer: "User token not authorized".
Wilma reports on console

[TOKEN] Checking token with IDM...
User access-token not authorized
Auth-token not found in request header

Keystone reports the same

"GET /v3/access-tokens/90ecf18114164f98b25668b9a940eb44 HTTP/1.1" 404

Why am i getting this access token not found when going through wilma but not for direct requests?

Edit: I also tried requesting domain scoped tokens but received same error.