Questions tagged [fiware-wilma]

FIWARE Wilma is the reference implementation of the PEP Proxy Generic Enabler specified within the FIWARE ecosystem. It works with both OAuth2 and XACML protocols

Wilma is an implementation of the FIWARE PEP Proxy Generic Enabler. The open standard specification for PEP proxies can be found here.

Wilma is used in combination with the Identity Management and Authorization PDP Generic Enablers to add authentication and authorization security to backend applications. This allows only specified users to access services. Policies and permissions can be managed down to the resource level allowing different access levels for different users.

Wilma is written in nodejs. The source code for the project can be found on GitHub. An official Docker image - fiware/pep-proxy - is also available.

The Documentation for Wilma can be found below:

57 questions
5
votes
1 answer

How to configure access control in Orion NGSI API for tenant isolation using Wilma PEP Proxy and IdM Keyrock?

I want to provide access control at the Orion Context Broker NGSI API level to ensure real data isolation. I want to make sure that a tenant can only query/update their contexts and NOT those of another tenant. To do so, I started putting an…
Emiliano Viotti
  • 1,619
  • 2
  • 16
  • 30
3
votes
1 answer

Fiware: How to restrict user access to specific entity for Orion Context Broker API using keystone & keypass

First of all, I'm using the Telefonica implementations of Identity Manager, Authorization PDP and PEP Proxy, instead of the Fiware reference implementations which are Keyrock, AuthZForce and Wilma PEP Proxy. The source code and reference…
Emiliano Viotti
  • 1,619
  • 2
  • 16
  • 30
3
votes
3 answers

Fiware - How to integrate Keyrock IdM, Wilma PEP Proxy and Orion Context Broker?

I read all the documentation of Keyrock and Wilma and I watched all the videos in the FIWARE Academy, but I still do not get success in this integration. I am searching for this since a few days ago, but without success. I think the FIWARE…
Dalton Cézane
  • 3,672
  • 2
  • 35
  • 60
3
votes
1 answer

Fiware KeyRock API bug: Membership of organisations not returned

As part of the FINISH accelerator we are using FIWARE KeyRock and Wirecloud. Currently we are using the Fiware labs global instance to investigate. We want to restrict our system so that users can only view data that belongs to the organisations of…
Robin
  • 103
  • 9
3
votes
4 answers

How to configure the Fiware PEP WILMA proxy to use a Keyrock and Orion instance on my own servers

I've spent most of the day trying to configure the Fiware PEP proxy Wilma to secure an Orion Context Broker i have running on a development server. The documentation here:…
Robin
  • 103
  • 9
2
votes
1 answer

Securing access to Orion Context Broker entities

I am searching for a solution, that the value of an attribute of a certain entity in the Orion Context Broker, which is secured with a Wilma PEP Proxy and Keyrock, can only be changed by a specific user (the one who created the entity). The Context…
gasp
  • 23
  • 3
2
votes
0 answers

Synchronicity / FIWARE: Error in IDM communication

we are deploying Synchronicity (https://gitlab.com/synchronicity-iot/platform-deployment-docker/-/tree/master/manual) using docker-compose with all the defaults that comes with the config files. Now we are facing a communication error between IdM…
Jordi
  • 21
  • 1
2
votes
1 answer

Error validating token. Proxy not authorized in keystone. Keystone authentication

I was trying to incorporate IDM (Docker) latest, and pep-proxy (git example running with node server). When I started pep-proxy, everything was working as intended. I've got the following messages: INFO: Server - Starting PEP proxy in port 80. IdM…
Igor
  • 225
  • 1
  • 9
2
votes
1 answer

Fiware - how to connect PEP proxy to Orion and configure both with HTTPS?

I am working with Orion and I try to protect the future apps using the PEP proxy and Keyrock, but I cannot find a way combine these 3 GE. All my base files are in this repository, although I have running Orion, Keyrock and Cygnus, I cannbot send…
2
votes
1 answer

Fiware Wilma PEP ssl protocol error at curl

I have at Fiware Lab a virtual machine deployed with Context Broker + Wilma Pep proxy. PEP is configured with https enabled at config.js config.https = { enabled =true...} Executing the command below I can see "https" process related to the node.js…
2
votes
1 answer

FIWARE - How Wilma PEP Proxy deal with redirection for multiple applications?

We are needing Wilma PEP Proxy control the access for many applications. I think it is not possible to do yet, with the latest Wilma version. Am I wrong? If I am wrong, how to deal with that? If I am right, is there some intention to make this…
2
votes
1 answer

Security for Southbound of lightweightm2m-iotagent?

Can i use the PEP proxy for lightweightm2m-iotagent ? is there any way to implement security for lightweightm2m-iotagent at southbound side(LWM2M Client to LWM2M Server) ?
English learner
  • 192
  • 1
  • 9
1
vote
3 answers

Orion APIs authentication through Keycloak

I want to add authentication on my Orion APIs through my Keycloak IdM. I know it is possible to use Orion together Pep Proxy Wilma and Keyrock to do this task, and a possible workaround can be to integrate keyrock with keycloak at this link (7 years…
pasquy73
  • 563
  • 3
  • 13
1
vote
0 answers

Unable to use JWT token generated from Fiware Keyrock

For the Fiware security layer Keyrock version 8.0.0, Wilma version 8.0.0 and Authzforce version release-10.0.0 are configured. Keyrock generates a Bearer token that works properly for Orion authorization. But, the problem comes if I use a JWT…
dacak
  • 60
  • 5
1
vote
0 answers

How to restrict user access to FIWARE Orion Subscriptions notifications with PEP proxy to authorized users only?

I am already using IDM together with Wilma PEP for access control to Orion. Now I want to achieve the same for outgoing notificaitons. Example: I have an app with users which for example shows devices. The user logs in and authenticates with FIWARE…
Christoph S
  • 697
  • 1
  • 6
  • 29
1
2 3 4