You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I try to use Fiware CKAN (Ckan with ckanext-oauth2 and ckanext-ngsiview) with a PEP-Proxy Wilma and I had a 401 error after setting Url to PEP-Proxy and "OAuth-Token" to required.
On the keyrock Log I found this :
STC-security_keyrock.1.8y6izg3ox6cq@vmlx | 2017-11-08 14:15:24.350 97 WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from 10.255.x.xx
STC-security_keyrock.1.8y6izg3ox6cq@vmlx | 2017-11-08 14:15:24.352 97 INFO eventlet.wsgi.server [-] 10.255.x.xx - - [08/Nov/2017 14:15:24] "GET /v3/access-tokens/whawIMPS03BZnYKn25XjDQEjCfHLzD HTTP/1.1" 401 334 4.029003
STC-security_keyrock.1.8y6izg3ox6cq@vmlx | 2017-11-08 14:15:24.434 97 INFO eventlet.wsgi.server [-] 10.255.x.xx - - [08/Nov/2017 14:15:24] "POST /v3/auth/tokens HTTP/1.1" 201 548 0.077919
On the Log of Pep-proxy Wilma :
2017-11-08 14:17:50.430 - INFO: IDM-Client - Checking token with IDM...
2017-11-08 14:17:54.449 - ERROR: IDM-Client - Error validating token. Proxy not authorized in keystone. Keystone authentication ...
2017-11-08 14:17:54.537 - ERROR: Server - Caught exception: SyntaxError: Unexpected token u
If I compare The HTTP request with Wirecloud/Pep-proxy Wilma (Pep work with Wirecloud with the same configuration) and Ckan/Pep-proxy Wilma : Wirecloud/Pep-proxy HTTP request :
POST /v1/queryContext?limit=100&details=on&offset=0 HTTP/1.1
user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 OPR/48.0.2685.52
accept: application/json
Content-Type: application/json
accept-language: en-US,en;q=0.8
x-forwarded-for: 10.12.x.xx, 172.17.x.xx,10.255.x.xx
fiware-service: test
fiware-servicepath: /oliv
x-real-ip: 10.12.x.xx
x-requested-with: XMLHttpRequest
x-auth-token: g8xYJGspvTtBMpI02fBOKeBBnR9REC
X-Nick-Name: user1
X-Display-Name: user1
X-Roles: [{"name":"Provider","id":"provider"}]
X-Organizations: []
Host: iot.test.org:1026
Content-Length: 63
Connection: close
Hi, I try to use Fiware CKAN (Ckan with ckanext-oauth2 and ckanext-ngsiview) with a PEP-Proxy Wilma and I had a 401 error after setting Url to PEP-Proxy and "OAuth-Token" to required.
On the keyrock Log I found this :
On the Log of Pep-proxy Wilma :
If I compare The HTTP request with Wirecloud/Pep-proxy Wilma (Pep work with Wirecloud with the same configuration) and Ckan/Pep-proxy Wilma :
Wirecloud/Pep-proxy HTTP request :
Ckan/Pep-proxy HTTP request :
{"entities": [{"type": "obj-test", "id": "test1", "isPattern": "false"}], "attributes": ["temperature"]}
I suspect ckanext-ngsiview don't send HTTP header X-Nick-Name: user1 ...
Thanks for help,
-Olivier.
The text was updated successfully, but these errors were encountered: