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
1
vote
1 answer

Fiware multitenancy

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…
piwo1984
  • 71
  • 6
1
vote
1 answer

How to configure FIWARE Components to avoid AZF domain not created for application response

Summary of the question: How can we let the FIWARE IdM Keyrock and the FIWARE Authzforce set properly the AZF domains, thus without getting "AZF domain not created for application XYZ" response? I'm trying to configure a server with FIWARE Orion,…
t.montanaro
  • 123
  • 11
1
vote
1 answer

Fiware IDM : Dynamic permission resource

I've deployed an application based on Fiware generic enablers, in Docker. The versions are: Orion 1.14 Cygnus 1.9.0 Authzforce 5.4.1 Keyrock: the latest Pep-proxy: 7.0.1 but, when I want to create a permission in keyrock I can't find a specific…
1
vote
0 answers

Fiware pep-proxy and idm communication issue

I wanted to connect pep-proxy with the idm .. so I followed the installation of pep from that link .. https://github.com/ging/fiware-pep-proxy by building it from the source . That was the config file i was supposed to edit // Credentials obtained…
ahmad emad
  • 172
  • 1
  • 13
1
vote
0 answers

FIWARE PEP Wilma 6.2 can't get a 'x-subject-token' when staring it

I try to protect orion with PEP Wilma 6.2. Although PEP proxy starts, It can't get a 'x-subject-token'. Why can't PEP get it? Is my configuration incorrect or insufficient? PEP Proxy Wilma 6.2 server.js:70 IDM.authenticate (function (token) { …
fisuda
  • 76
  • 4
1
vote
0 answers

Fiware - Configure AuthZForce with PEP Proxy

I deployed Orion, Cygnus, Keyrock and PEP proxy using docker compose as you can see on the repository. But the security level implemented is not the desired. keystone_url = "http://localhost:5000" keyrock_url = "http://localhost:8000" orion …
1
vote
1 answer

Authzforce does not store policies?

I am developing a new application using Fiware and I am interested in adding a security layer using the specific Fiware GE for this: IdM Keyrock Wilma PEP Proxy AuthZForce PDP I started by setting up my own local installation of these components,…
Emiliano Viotti
  • 1,619
  • 2
  • 16
  • 30
1
vote
1 answer

How can AuthForce be configured for scaling?

We are building an scenario where we are going to need more than 1 AuthForce using only 1 IdM. Can anyone help as to how we could configure this scenario?
David Lose
  • 39
  • 3
1
vote
0 answers

XACML policies are not sync with AuthZForce after creation in IdM

Im trying to extend the Wilma PEP Proxy GE to support level 3 of security: xacml authorization. I already implemented the necessary modifications in the PEP Proxy, in order to support this level of authorization, but I'm having problems…
Emiliano Viotti
  • 1,619
  • 2
  • 16
  • 30
1
vote
1 answer

Configuring Orion Context Broker, Wilma PEP Proxy and Keyrock IdM

My name is Joe and I'm in traineeship about IoT security and Identity Management. In order to develop some solutions to a project I've been assigned, I have to configure and integrate Orion, Wilma and Keyrock (and potentially a PDP, but that comes…
Giuseppe
  • 17
  • 1
  • 7
1
vote
1 answer

How to properly configure IoT sensors in order to gain authentication and authorization using IdM Keyrock and Wilma PEP Proxy

I have being working for some weeks with the IdM Keyrock, Wilma PEP Proxy and AuthZForce in the context of Fiware Platform, in order to develop an IoT application. I had success in protecting the Orion Context Broker APIs using Wilma PEP Proxy and…
1
vote
1 answer

Fiware AuthZForce error: "AZF domain not created for application"

I'm trying to protect Orion Context Broker using KeyRock idm, Wilma PEP-Proxy and AuthZForce PDP over Docker. For now, level 1 security works well and I can deny access to non logged users, but I get this error on Wilma when trying to add level…
1
vote
0 answers

Fiware - Wilma PEP Proxy does not validate SSL certificate

I have a scenario in which I want Wilma PEP Proxy redirecting to a server via HTTPS. This is working now, but the server certificate (self-signed) is not being validated. In the config.js file, the only configuration about this is the…
Dalton Cézane
  • 3,672
  • 2
  • 35
  • 60
1
vote
2 answers

FIWARE - PEP Proxy configured to HTTPS

I would like to know how I configure the PEP Proxy so that I can exchange messages through HTTPS. I have an instance of Orion context broker that is accessed only after pass by the PEP Proxy. My PEP Proxy (Wilma) configuration file (config.js) has…
Dalton Cézane
  • 3,672
  • 2
  • 35
  • 60
1
vote
2 answers

How to work with DELETE request and X-Auth-Token

I want DELETE operation be allowed only after authentication/authorization process. I tried to do a DELETE operation passing an X-Auth-Token, but I got this: The status of this operation is: 400 Some error occurred! …
Dalton Cézane
  • 3,672
  • 2
  • 35
  • 60