Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:Apps
-
HD-Enabler:Wirecloud
Description
Created question in FIWARE Q/A platform on 01-05-2016 at 01:05
Please, ANSWER this question AT http://stackoverflow.com/questions/36961272/fiware-wirecloud-error-using-x-fi-ware-oauth-token-request-header
Question:
FIWARE Wirecloud: Error using X-FI-WARE-OAuth-Token request header
Description:
We are part of the FINISH accelerator and are deploying Wirecloud and KeyRock on our own servers using the docker containers provided by fiware.
We have KeyRock-IdM set up and linked to Wirecloud. We are trying to pass the logged-in users token to an API which returns data to a widget.
We found documentation about the "X-FI-WARE..." headers in the github code and wrote a test widget (main.js shown below). When deployed on the fiware labs instance, it works out of the box. When deployed on our local installation with a docker container it gives the following error: "Current user has not an active FIWARE profile". I scoured the settings.py file but have no idea where this error is coming from. I have DEBUG=True but nothing show up in the log. The user running the widget was logged in through the KeyRock IdM.
/*jshint globalstrict:true */
/global MashupPlatform, ObjectStorageAPI, StyledElements/
(function () {
"use strict";
var token_available = MashupPlatform.context.get('fiware_token_available');
var username = MashupPlatform.context.get('username');
alert(username + " has token?: " + token_available);
var url = MashupPlatform.prefs.get('keyRock_url');
var request = MashupPlatform.http.makeRequest(url, {
requestHeaders:
,
method: "GET",
onSuccess: function (response)
,
onFailure: function (response)
,
onComplete: function () {
}
}
);
})();
How can i find out what is going wrong?
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
5h 59m | 1 | Backlog Manager | 01/May/16 9:02 AM | |||||
|
3h | 1 | Backlog Manager | 01/May/16 12:02 PM | |||||
|
5d 6h 4m | 1 | Backlog Manager | 06/May/16 6:07 PM |
Fix Version/s | 2021 [ 12600 ] |
Summary | FIWARE.Question.Tech.Apps.ApplicationMashup.ComponentDevelopment.ErrorUsingTheX-FI-WARE-OAuth-TokenHeader | FIWARE.Question.Tech.Apps.ApplicationMashup.ComponentDevelopment.ErrorUsingIdMTokenHeader |
Summary | FIWARE.Question.Tech.Apps.ApplicationMashup.FIWARE Wirecloud: Error using X-FI-WARE-OAuth-Token request header | FIWARE.Question.Tech.Apps.ApplicationMashup.ComponentDevelopment.ErrorUsingTheX-FI-WARE-OAuth-TokenHeader |
Summary | [fiware-stackoverflow] FIWARE Wirecloud: Error using X-FI-WARE-OAuth-Token request header | FIWARE.Question.Tech.Apps.ApplicationMashup.FIWARE Wirecloud: Error using X-FI-WARE-OAuth-Token request header |
HD-Node | Unknown [ 10852 ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Assignee | Álvaro Arranz [ aarranz ] |
HD-Chapter | Unknown [ 10845 ] | Apps [ 10836 ] |
HD-Enabler | Unknown [ 10910 ] | Wirecloud [ 10857 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
HD-Enabler | Unknown [ 10910 ] | |
HD-Chapter | Unknown [ 10845 ] | |
HD-Node | Unknown [ 10852 ] |
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
2016-05-06 18:05|UPDATED status: transition Finish| # answers= 3, accepted answer= True