Details
-
Type:
Monitor
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
HD-Chapter:Data
-
HD-Enabler:Orion
Description
Created question in FIWARE Q/A platform on 09-04-2017 at 09:04
Please, ANSWER this question AT https://ask.fiware.org/question/784/how-to-control-access-to-orion-using-oauth-20/
Question:
How to control access to Orion using oauth 2.0?
Description:
Hi.
I can access the entity named 'TestRoom' in Orion using request like 'http://localhost:1026/v2/entities/TestRoom' without any access restrictions.
So, I just want to make constraint to access Test_Room using OAuth2.0 token.
But now I don't know how to make access token scope to entity in Orion.
For example, I want to make the user or the app that has access token(scope:read temperature from TestRoom) can read temperature information from TestRoom.
If I know above thing, I will make the request access token(scope:read info. from Test_Room) and use that token with X-Auth-Token header.
So Could you get me any information, URL or document?
I already read RFC 6749 and some documents of FIWARE Security GE, and installed orion, keyrock and authzforce.
And I was not install the Willma(PEP) because Tour-Guide App provided FIWARE doesn't use this GE.
(I don't know why, as you know, PEP is entry point of all FIWARE security right?)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Fermín Galán [ fermin ] |
| Component/s | FIWARE-TECH-HELP [ 10278 ] |
| HD-Enabler | Orion [ 10875 ] | |
| Description |
Created question in FIWARE Q/A platform on 09-04-2017 at 09:04 {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/784/how-to-control-access-to-orion-using-oauth-20/ +Question:+ How to control access to Orion using oauth 2.0? +Description:+ Hi. I can access the entity named 'TestRoom' in Orion using request like 'http://localhost:1026/v2/entities/TestRoom' without any access restrictions. So, I just want to make constraint to access Test_Room using OAuth2.0 token. But now I don't know how to make access token scope to entity in Orion. For example, I want to make the user or the app that has access token(scope:read temperature from TestRoom) can read temperature information from TestRoom. If I know above thing, I will make the request access token(scope:read info. from Test_Room) and use that token with X-Auth-Token header. So Could you get me any information, URL or document? I already read RFC 6749 and some documents of FIWARE Security GE, and installed orion, keyrock and authzforce. And I was not install the Willma(PEP) because Tour-Guide App provided FIWARE doesn't use this GE. (I don't know why, as you know, PEP is entry point of all FIWARE security right?) |
Created question in FIWARE Q/A platform on 09-04-2017 at 09:04
{color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/784/how-to-control-access-to-orion-using-oauth-20/ +Question:+ How to control access to Orion using oauth 2.0? +Description:+ Hi. I can access the entity named 'TestRoom' in Orion using request like 'http://localhost:1026/v2/entities/TestRoom' without any access restrictions. So, I just want to make constraint to access Test_Room using OAuth2.0 token. But now I don't know how to make access token scope to entity in Orion. For example, I want to make the user or the app that has access token(scope:read temperature from TestRoom) can read temperature information from TestRoom. If I know above thing, I will make the request access token(scope:read info. from Test_Room) and use that token with X-Auth-Token header. So Could you get me any information, URL or document? I already read RFC 6749 and some documents of FIWARE Security GE, and installed orion, keyrock and authzforce. And I was not install the Willma(PEP) because Tour-Guide App provided FIWARE doesn't use this GE. (I don't know why, as you know, PEP is entry point of all FIWARE security right?) |
| HD-Chapter | Data [ 10838 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
2017-12-18 16:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
2017-12-18 17:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False
| Assignee | Fermín Galán [ fermin ] | Jose Manuel Cantera [ jmcantera ] |
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
| Fix Version/s | 2021 [ 12600 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
253d 1h 52m | 1 | Backlog Manager | 18/Dec/17 3:56 PM | |||||
|
1h | 1 | Backlog Manager | 18/Dec/17 4:56 PM | |||||
|
24d 15h 38m | 1 | Fernando Lopez | 12/Jan/18 8:35 AM |
2017-04-09 15:05|CREATED monitor | # answers= 0, accepted answer= False