Hi everyone, Today we will run presentation on several incubated FIWARE GEs that have been proposed: Endpoint-Auth-Service The Endpoint-Auth-Service transparently adds authentication and authorization information to outgoing http-requests for configured endpoints and components. The service either brings a sidecar-proxy(envoy) or integrates into an already existing service mesh to intercept the requests and handle them according to configuration applied through its API. It allows to connect Context-Brokers or similar components to secured data-sharing environments like i4trust or any secured recipient without changing the code of the component itself. This decouples the security concern from the actual logic and allows to use already existing libraries or auth-solutions, instead of adapting to the technical restrictions of the implementation. Apollo FIWARE Apollo offers an API to receive NGSI-LD compliant notifications and translates them into NGSI-LD compliant entity creation and update requests to be sent to a compliant Context-Broker. It autonomously checks the existence of received entities and either updates them via PATCH or creates them through a POST request. The provided API allows to connect and synchronize entities through multiple Context-Brokers through the use of NGIS-LD subscriptions. Apollo can support multi-tenancy through parallel installations, due to its ability to apply specific tenancy information. FIWARE Kong Plugins What: You get plugins for the popular API Gateway Kong which allow to integrate with the FIWARE ecosystem. Depending on the scenario and environment, these plugins allow to extend the Kong API Gateway framework with PEP and/or PDP functionalities, so that the Kong API Gateway can be added to implement access management to backend applications. There are different plugins provided, covering PEP functionalities in connection to a PDP component, or providing the capabilities to perform decentralised access management in the context of data spaces. Why: Kong is one of the most popular API Gateways with a strong community. It is a Lua application running in Nginx and provides functionalities like load balancing, logging and transformations. Through plugins, it can be extended to support several authentication and authorization mechanisms. These plugins allow to easily integrate environments using Kong into the FIWARE Ecosystem. When setting up a FIWARE-based solution, the usage of Kong provides a could-native and platform-agnostic API Gateway. This GE also incorporates the following FIWARE Lua library: https://github.com/FIWARE/lua-fiware-lib Once the presentations are made, we will leave the standard one week to raise comments/amendments/objections so that we can take a formal decision during the next TSC planned on July 18th. Cheers, -- Document Juanjo Hierro Chief Technology Officer juanjose.hierro at fiware.org www.linkedin.com/in/jhierro <https://www.linkedin.com/in/jhierro> Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro <https://twitter.com/JuanjoHierro> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20220711/4e4eb141/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: foundation-logo.png Type: image/png Size: 8201 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20220711/4e4eb141/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy