Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Dismissed
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:Security
-
HD-Enabler:Wilma
Description
Created question in FIWARE Q/A platform on 29-04-2016 at 01:04
Please, ANSWER this question AT https://stackoverflow.com/questions/36927066/fiware-wilma-pep-proxy-bug-x-organisations-header-value-contains-rubbish
Question:
FIWARE Wilma PEP Proxy bug: x-organisations header value contains rubbish
Description:
I want to restrict data that is retrieved from a back-end server to organisations to which the authenticated user is a member.
From the documentation (https://github.com/ging/fiware-pep-proxy) this should be possible using Wilma's inbuilt function for populating a number of http headers:
Once authenticated, the forwarded request will include additional HTTP >headers with user info:
X-Nick-Name: nickname of the user in IdM
X-Display-Name: display name of user in IdM
X-Roles: roles of the user in IdM
X-Organizations: organizations in IdM
However the actual values of the last two headers as forwarded are:
'x-roles': '[object Object]',
'x-organizations': '[object Object]',
The headers literally contain a string value "[object Object]" rendering them completely useless. It looks like the author forgot to serialize the roles and organisations data.
Please tell me i am overlooking something here?
If not, any chance of a timely fix? I am not a javascript guru, but a quick google search tells me "JSON.stringify" should do the trick.
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
Assignee | Alvaro Alonso [ aalonsog ] |
HD-Enabler | KeyRock [ 10889 ] | |
Description |
Created question in FIWARE Q/A platform on 29-04-2016 at 01:04 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/36927066/fiware-wilma-pep-proxy-bug-x-organisations-header-value-contains-rubbish +Question:+ FIWARE Wilma PEP Proxy bug: x-organisations header value contains rubbish +Description:+ I want to restrict data that is retrieved from a back-end server to organisations to which the authenticated user is a member. From the documentation (https://github.com/ging/fiware-pep-proxy) this should be possible using Wilma's inbuilt function for populating a number of http headers: Once authenticated, the forwarded request will include additional HTTP >headers with user info: X-Nick-Name: nickname of the user in IdM X-Display-Name: display name of user in IdM X-Roles: roles of the user in IdM X-Organizations: organizations in IdM However the actual values of the last two headers as forwarded are: 'x-roles': '[object Object]', 'x-organizations': '[object Object]', The headers literally contain a string value "[object Object]" rendering them completely useless. It looks like the author forgot to serialize the roles and organisations data. Please tell me i am overlooking something here? If not, any chance of a timely fix? I am not a javascript guru, but a quick google search tells me "JSON.stringify" should do the trick. |
Created question in FIWARE Q/A platform on 29-04-2016 at 01:04
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/36927066/fiware-wilma-pep-proxy-bug-x-organisations-header-value-contains-rubbish +Question:+ FIWARE Wilma PEP Proxy bug: x-organisations header value contains rubbish +Description:+ I want to restrict data that is retrieved from a back-end server to organisations to which the authenticated user is a member. From the documentation (https://github.com/ging/fiware-pep-proxy) this should be possible using Wilma's inbuilt function for populating a number of http headers: Once authenticated, the forwarded request will include additional HTTP >headers with user info: X-Nick-Name: nickname of the user in IdM X-Display-Name: display name of user in IdM X-Roles: roles of the user in IdM X-Organizations: organizations in IdM However the actual values of the last two headers as forwarded are: 'x-roles': '[object Object]', 'x-organizations': '[object Object]', The headers literally contain a string value "[object Object]" rendering them completely useless. It looks like the author forgot to serialize the roles and organisations data. Please tell me i am overlooking something here? If not, any chance of a timely fix? I am not a javascript guru, but a quick google search tells me "JSON.stringify" should do the trick. |
HD-Chapter | Security [ 10841 ] |
HD-Enabler | KeyRock [ 10889 ] | Wilma [ 10890 ] |
Resolution | Dismissed [ 10102 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Fix Version/s | 2021 [ 12600 ] |