fiware-wilma

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

由 ⅰ亾dé卋堺 提交于 2019-12-29 01:53:30
问题 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 documentation could have tutorials, hands on... I have a VM with Orion Context Broker and a container with Keyrock IdM and Wilma PEP Proxy. I am trying to generate an access token to grant access for an application, but I still did not get it. Besides, I

FIWARE AuthZForce 5.4.1 is not installing

由 橙三吉。 提交于 2019-12-25 13:39:12
问题 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 currently installed.) Preparing to unpack authzforce-ce-server-dist-5.4.1.deb ... Unpacking authzforce-ce-server (5.4.1) over (5.4.1) ... Setting up authzforce-ce-server (5.4.1) ... * Starting Tomcat servlet engine tomcat7 [fail] dpkg: error

Fiware IDM+AuthZForce+PEP-Proxy-Wilma

由 别说谁变了你拦得住时间么 提交于 2019-12-25 08:47:49
问题 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 files and nothing changed. I tried to populate the database (mongoDB or PostgreSQL) and nothing changed, too. All services are running in a docker-compose instance. Anyonce already has deployed this successfully? 回答1: I think you can get some help

Can anyone explain the usage of Context Broker via PeP proxy?

由 久未见 提交于 2019-12-24 11:32:50
问题 I have installed orion Context Broker and pep proxy on my machine. I am targeting the global instance of keyRock and the AuthZforce to authenticate the context broker. Here is my config.js: var config = {}; config.pep_port = 1307; // Set this var to undefined if you don't want the server to listen on HTTPS config.https = { enabled: false, cert_file: 'cert/cert.crt', key_file: 'cert/key.key', port: 443 }; config.account_host = 'https://account.lab.fiware.org'; config.keystone_host = 'cloud.lab

Fiware IDM : Dynamic permission resource

由 六月ゝ 毕业季﹏ 提交于 2019-12-24 10:59:50
问题 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 syntax or character sequence to enter a dynamic resource in the resource field like: /resource1/<user>/info , or to specify only the resource prefix like: /resource2/<whatever> . Really exists the syntax for the dynamic resource and authzforce can

Fiware : wilma vs steelskin

由 给你一囗甜甜゛ 提交于 2019-12-13 02:35:53
问题 when to use wilma and when to use steelskin? why there is no reference of steelskin in fiware generic enablers catalogue? Thanks in advance for your help! 回答1: Wilma is an official FIWARE enabler. Steelskin is not part of FIWARE, but is developed by some people that are very involved in FIWARE (from Telefonica) and is mostly compatible. So if you want to be 100% FIWARE compliant go with Wilma. If you don't care then it may be interesting to research further on Steelskin. 来源： https:/

Fiware Keyrock - organizations are not returned

由 我们两清 提交于 2019-12-12 05:12:56
问题 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. Even the owner of the organization receives an empty list. Is this a bug? What can we do to get this information? In my local instance I just get to do up to step 7 of this tutorial: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php

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

由 ∥☆過路亽．° 提交于 2019-12-07 11:45:35
问题 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: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/PEP_Proxy_-Wilma-_Installation_and_Administration_Guide is not clear. Here is my setup: A Fiware Keyrock instance running on server1, port 3000 A PEP Proxy running on server 1 An Orion Context Broker running on server2, port 1026 The manual states to edit the

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

由 我与影子孤独终老i 提交于 2019-12-06 02:09:11
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: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/PEP_Proxy_- Wilma -_Installation_and_Administration_Guide is not clear. Here is my setup: A Fiware Keyrock instance running on server1, port 3000 A PEP Proxy running on server 1 An Orion Context Broker running on server2, port 1026 The manual states to edit the config.js script. Here is what i changed (Stackoverflow prevents me from entering url's so replace

AuthZForce Security Level 2: Basic Authorization error “AZF domain not created for application”

由 独自空忆成欢 提交于 2019-11-30 20:19:27
问题 We are trying to deploy our security layer (KeyRock, Wilma, AuthZForce) to protect our Orion instance. We are able to have security level 1 (authentication) with Keyrock and Wilma working, but when we try to insert AuthZForce to check the verb+resource authorization we get the error message: AZF domain not created for application In the PEP Proxy User Guide, under "Level 2: Basic Authorization" section, it is stated that we have to configure the roles and permissions for the user in the
订阅 fiware-wilma