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
0
votes
0 answers

Domain not found: AZF domain not created for application

I got this error while trying to configure level 2 authentication using idm,pep-proxy and pdp. I am using latest version of authzforce,idm,pep-proxy but this error still persists. config.azf = { enabled: true, protocol: 'http', host:…
Igor
  • 225
  • 1
  • 9
0
votes
1 answer

Fiware IDM+AuthZForce+PEP-Proxy-Wilma

I'm trying to put to work the IDM+AuthZForce+PEP-Proxy-Wilma to secure the Orion context broker, but I'm having a bit of trouble, nothing works, all is up and running, but there's no autentication and no security. I changed all the configuration…
Naff16
  • 83
  • 1
  • 9
0
votes
1 answer

FIWARE AuthZForce 5.4.1 is not installing

I am trying to install FIWARE AuthZForce 5.4.1, following the official documentation, but with no success because the Tomcat7 is not starting during the installation process as can be seen below. (Reading database ... 40187 files and directories…
Dalton Cézane
  • 3,672
  • 2
  • 35
  • 60
0
votes
1 answer

FIWARE - Is there some Cryptographic GE or a GE with this kind of functionality?

I would like to know if there are only the Security GEs exposed in the Fiware catalogue. Specifically, I am interested in one component that can do cryptographic functions, like generate and provide key pairs, encrypt, decrypt, etc. If the answer is…
Dalton Cézane
  • 3,672
  • 2
  • 35
  • 60
0
votes
1 answer

Fiware Keyrock - organizations are not returned

I am needing the organizations info, from a specific user. This information is not returned as can be seen below: organizations: [], displayName: 'idm', roles: [ { name: 'Provider', id: 'provider' } ], I am getting an empty list of organizations.…
0
votes
1 answer

What does the magic key do in Wilma and AZF?

I would like to know the real use of the magic key parameter at Wilma PEP Proxy as well in the AZF. Is this mandatory in both configuration? If not, when do we need to use it? I saw that there is bug related to it described here
0
votes
1 answer

The roles generated in Keyrock are not really registered

I am creating a permission for an application in Keyrock and associating it to user A. When I do a GET request to orion v2/entities (that is equal to created permission), I get a User token not authorized message. In the PEP log I can see that the…
0
votes
1 answer

FIWARE-Keyrock: Why are the OAuth2 credentials related to apps if they do not control access?

We have a scenario where I want to protect a service X with Wilma PEP Proxy. The service X is registered in Keyrock. The Wilma PEP Proxy contains the PEP credentials generated in Keyrock for service X. An application Y gets access to service X with…
0
votes
1 answer

FIWARE - Keyrock tokens with general permission enabling unauthorized access to applications (security issue?)

In a local Keyrock instance, we have two users, A and B, with two different applications, AppA and AppB, respectively. Both users are distinct from the default "admin" user "idm". The Wilma PEP Proxy is configured with PEP credentials from user A.…
Dalton Cézane
  • 3,672
  • 2
  • 35
  • 60
0
votes
1 answer

FIWARE AuthZForce doesn't check the second rule inside the same PolicySet

I have created two roles, on the KeyRock, and for each of them I have linked a different permission User1->Role1->Perm1(access to Res1) User2->Role2->Perm2(access to Res2) After saved, I see on AuthZforce's file system a new domain that it has 3…
alaporta
  • 21
  • 1
0
votes
1 answer

Keyrock vs OpenStack

I am trying to understand what are really the changes done on Keystone and Horizon forks by GING and are these needed only for the Fiware Lab (i.e. are the Fiware Lab specific)? We are making our proper Fiware installation for Mainflux IoT Cloud:…
Drasko DRASKOVIC
  • 343
  • 1
  • 3
  • 8
0
votes
1 answer

Problems creating a domain in Fiware AuthZforce Authorization Server

I'm developing an authentication/authorization scheme, based on Oauth 2.0, using the Fiware Enablers: Keyrock IdM, Wilma Proxy and AuthZforce authorizaton server. I installed and configured Keyrock and Wilma and they work fine together. On the same…
mgucc
  • 1
  • 2
1 2 3
4