I already found this question, I will quote it since problem seem to be happening again "I'm creating a Wirecloud Mashup using ngsi-source operator. Until some days ago everything worked very well but now the NGSI Proxy http://ngsiproxy.lab.fiware.org seems not to be alive".
Are there issues with this service? Unfortunately I cannot use the instance at https://mashup.lab.fiware.org:8443 as I need ngsi proxy over http.
Thanks for the answers.
The instance at http://ngsiproxy.lab.fiware.org is currently up and running (August the 16th). I don't know the status of the service on August the 10th.
NOTE:
Take into account that, https://mashup.lab.fiware.org:8443 is not longer available.
Related
We are evaluating several platforms for integrating a "Smart Energy System".
One important requirement we have to support is multitenancy. From the docs I can see the possibility to start the Orion Context Broker with this option. Orion will ensure the data separation based on the fiware-service request header.
That's fine but how to "secure" this header across the whole software stack (PEP-Proxy, IoT-Agent)?
Which component/device sets this header? Which component ensures that a request with a specific fiware-service header value is authorized to access the data of this tenant?
In my opinion this is a task for Wilma as PEP-Proxy. All traffic to Orion is routed through the PEP-Proxy and the proxy checks if this request is valid. Unfortunately I can not find such a check within the source code nor it is explained in the documentation.
Has someone implemented such an architecture an can help me?
Found another post which answers my question
How to configure access control in Orion NGSI API for tenant isolation using Wilma PEP Proxy and IdM Keyrock?
We will have to implement this kind of authorization for our own.
I am new to Charles Proxy. As far as I have read, it gives me ability to see all the calls happening from within my application.
Is there any difference between what we can do using Charles Proxy and Chrome -> Inspect Element -> Network ?
My requirement is as follows:
I would like to see all the calls (specifically API calls) being made by the application I am browsing and that is to any levels.
Is this possible by any of them?
I am seeing one level API call but not any further (i.e. not multi-level).
Is this because none of the captures server to server API calls, which I feel should be.
Please let me know if any further information is needed to get the whole context.
After a bit more exploring found answer to the question
"I would like to see all the calls (specifically API calls) being made by the application I am browsing and that is to any levels."
This is possible through Charles Proxy but we need to have the application running in local. This is obvious server to server API calls will not be exposed so as a developer if he/she wants to get the any-level API calls being made by the application that he/she is trying to explore, the solution will be to setup the application locally and configure Charles Proxy.
Please share if anyone wants to share any other thought.
I am developing a service agent where I want to know when the values of sensor are changed. Instead of developing an automatic http request in my service to query context broker (each 15 mins or so) I want to know if I can configure cygnus to notify me of these changes?
Im doing this because I want to put the data coming from my sensors in an algorithm that detects certain trends.
Thank you, I hope my question is clear enough.
If you are not an experienced user of fiware technologies please ignore this question.
Probably it is better that you subscribe and end point (integrated with your service) to orion so your service is notified when the sensor value change.
https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide#Context_subscriptions
Do you really need to use Cygnus?
I'm trying to integrate Proton CEP and Mandrill, an email service, mediated by Orion context broker.
When I was starting to study Orion, I thought that it would be able to communicate directly with CEP, exchanging JSON objects through http. And also that Orion would be able to parse each object to deliver to the correct format understandable by each API.
From the examples and documentation available I was able to understand that another API developed by us should be doing the parsing and mediating the communications between each API.
So I'd like to confirm that this is so and that I'm not missing something. Is Orion indeed unable to customize its outputs?
If confirmed, then I will proceed with development of this mediating API.
Arthur
Edit:
I believe I wasn't clear above about the issue. I hope adding this helps.
Proton CEP recieves through http POST JSON objects, but it only understands the variables if they are in simple format, like {"Name1":"Value1","Name2":"Value2"}, with no arrays or complex struture.
Orion, can comunicate in JSON as well through http, but I can't control the structure of the JSON output. So the result is that CEP wouldn't be able to understand inputs from Orion and process them. The same issue arises with other APIs too. And I'd like to confirm that Orion is indeed unable to custom its output and that this integration needs to be done on our side.
You can find best explanation about connection between CEP and Orion in latest guides.
User guide's Appendix A specifies steps to establish such a communication (subscription(s) and/or simple publish).
Orion only understands/returns XML and JSON, and with this it is able to communicate with most of the GEs in FIWARE. I can't tell you anything about the Proton CEP, sorry.
To make sure you have interoperability between GEs (and especially other components) a "mediating gateway" will solve the problem, of course.
The JSON format that Orion Context Broker sends in notification conforms to the NGSI10 context management specification. Using a predefined JSON (instead of a custom one) is the best way to ensure that interoperability with other NGSI-compliant software works.
Before doing the NGSI-to-Proton adaptation piece yourself, I'd recomend you to check with Proton development team if there is any existing NGSI connector to their system that you can reuse. You can find contact details in Proton page at FIWARE catalogue.
is either of the two available PEP proxies for Orion (i.e. either /fiware-orion-pep or /fi-ware-pep-proxy) able to use Keycloak's IDM instead of Keystone's ? if not, are there plans to make this functionality available?
I'm afraid they aren't. About the inclusion in the roadmap, it is not expected AFAIK, at least in 'fiware-orion-pep'. There are means, though, to integrate Keystone with other authentication providers (SAML, OpenID...), so maybe you should try to integrate THROUGH Keystone instead of replacing it with other authentication provider.