Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Security
-
HD-Enabler:Wilma
Description
Good morning,
I have two issues concerning Fiware Orion:
First:
I am following the Fiware context broker introduction to get a token from
the Orion public instance as described in:
https://fiware-orion.readthedocs.io/en/develop/quick_start_guide/index.html.
<https://fiware-orion.readthedocs.io/en/develop/quick_start_guide/index.html>
<https://fiware-orion.readthedocs.io/en/develop/quick_start_guide/index.html>
- wget --no-check-certificate
https://raw.githubusercontent.com/fgalan/oauth2-example-orion-client/master/token_script.sh - bash token_script.sh
Last week I downloaded the script, executed it, and after specifying my
Fiware-Lab credentials I got the needed token. This week, however, when I
run the script, I receive an empty response.
Second:
If I were to use one of my personal Orion Instances in Fiware Cloud, how is
the authentication manages? Do I need to install an IDM or is it already
configured to do so?
If you could give me an insight on what I should do, I would really
appreciate it.
Oihane
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Oihane Kamara Esteban <oihane.esteban@deusto.es>]
Activity
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
1d 6h 37m | 1 | Fermín Galán | 14/Oct/16 4:29 PM | |||||
|
10d 18h 27m | 1 | Alvaro Alonso | 25/Oct/16 10:57 AM | |||||
|
1s | 1 | Alvaro Alonso | 25/Oct/16 10:57 AM |
| Fix Version/s | 2021 [ 12600 ] |
| Summary | [Fiware-tech-help] Fiware Orion Context Broker - can not get token | FIWARE.Request.Tech.Security.PEP-Proxy.Fiware Orion Context Broker - can not get token |
| HD-Chapter | Security [ 10841 ] | |
| HD-Node | Unknown [ 10852 ] |
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
| HD-Chapter | Security [ 10841 ] |
| Assignee | Alvaro Alonso [ aalonsog ] |
| HD-Chapter | Data [ 10838 ] | Security [ 10841 ] |
| Assignee | Manuel Escriche [ mev ] |
| HD-Enabler | Orion [ 10875 ] | Wilma [ 10890 ] |
Manuel, I have assigned the issue to you in the hope you can assign in sequence to the experts in the security chapter regarding the second question (see my last comment). Thanks!
| Assignee | Fermín Galán [ fermin ] | Manuel Escriche [ mev ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Regarding first question, please have a look to this ticket: https://jira.fiware.org/browse/HELP-7484. The cause is probably the same and now it should work again.
Regarding the second question, you would typically install a PEP proxy to protect your Orion API instance. Then, that PEP proxy be connected either 1) the global IDM and Access Control componentes associated to the FIWARE Lab cloud, 2) your own private instances of IDM and Access Control. However, I'm not an expert in the FIWARE security framework so I'll tell the people in charge of JIRA that assign the ticket to some expert in that area.
| Assignee | Fermín Galán [ fermin ] |
| HD-Chapter | Unknown [ 10845 ] | Data [ 10838 ] |
| HD-Enabler | Unknown [ 10910 ] | Orion [ 10875 ] |
| HD-Enabler | Unknown [ 10910 ] | |
| HD-Chapter | Unknown [ 10845 ] | |
| HD-Node | Unknown [ 10852 ] |
| Field | Original Value | New Value |
|---|---|---|
| Component/s | FIWARE-TECH-HELP [ 10278 ] |
AS Fermín has explained you can deploy a Wilma PEP Proxy instance on top of your CB instance to protect the API. And you can configure it to validate the requests with the central FIWARE Lab IdM instance. You can see details about how this work in the Wilma documentation and courses (https://catalogue.fiware.org/enablers/pep-proxy-wilma)