Fermín Galán Márquez
Fermín Galán Márquez
**Is your feature request related to a problem / use case? Please describe.** Include the previous values of attributes in the context available for JEXL expression evaluation **Describe the solution...
**Is your feature request related to a problem / use case? Please describe.** Currently we can add and modify attribute values in custom notification using `ngsi` field (NGSI patching), but...
geo:point is deprecated (https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/deprecated.md) so its support should be removed from Cygnus at some point. Check usage in projects before remove it.
Fixes [https://github.com/telefonicaid/fiware-orion/security/code-scanning/1](https://github.com/telefonicaid/fiware-orion/security/code-scanning/1) To fix the problem, we need to ensure that detailed error messages, including stack traces, are not exposed to the end users. Instead, we should log the detailed...
Fixes [https://github.com/telefonicaid/fiware-orion/security/code-scanning/2](https://github.com/telefonicaid/fiware-orion/security/code-scanning/2) To fix the reflected server-side cross-site scripting vulnerability, we need to ensure that any user-provided data is properly escaped before being included in the response. In Python, the...
NGSIv1 API was gradually removed from Orion 2.6.0 to 4.0.0, but a lot of dead code remains. This PR removes that dead code.
Registration documents are this way: ``` { "_id": ObjectId("5149f60cf0075f2fabca43da"), "format": "JSON", "fwdMode": "all", "expiration": 1360232760, "contextRegistration": [ { "entities": [ { "id": "E1", "type": "T1", "isPattern": "false" }, { "id":...
Deprecated since Orion 2.0.0, almost all NGSIv1 stuff was removed in Orion 4.0.0. However, the legacyForwarding logic is still there. Rule R90 should be added to https://github.com/telefonicaid/fiware-orion/tree/master/scripts/oriondb_consistency
Now that IOTA-UL is officially deprecated (see https://github.com/telefonicaid/iotagent-ul/pull/695) a documentation explaining how to migrate from it to IOTA-JSON would be desirable.
In some cases having this situation: * expr1 with evalPriority1 (e.g. 4) * expr2 with depending on expr1 but with evalPriority2 lower (e.g. 2) It may happen that expr2 gets...