Questions tagged [fiware-keyrock]

FIWARE Keyrock is the reference implementation of the Identity Manager (IdM) Generic Enabler specification. It is based on Openstack Horizon and Keystone.

Keyrock is responsible for authentication and authorization processes, together with PEP Proxy. An application or a user, that wants to access a protected service, authenticates with Keyrock IdM and gets an OAuth2 token. With this token, the application/user requests something to the protected service, reaching the PEP Proxy. The PEP Proxy gets the received token and validates it with Keyrock IdM. Once the token is valid, the application/user gets successful access to the protected service; otherwise, the access is denied.

Currently, the main concepts of Keyrock are:

  • Users
    • Have a registered account in Keyrock.
    • Can manage organizations and register applications.
  • Organizations
    • Are group of users that share resources of an application (roles and permissions).
    • Users can be members or owners (manage the organization).
  • Applications
    • It has the client role in the OAuth 2.0 architecture and will request protected user data. More information can be found in OAuth section.
    • Are able to authenticate users using their Oauth credentials (id and secret) which unequivocally identify the application.
    • Define roles and permissions to manage authorization of users and organizations.
    • Can register Pep Proxy to protect backends.
    • Can register IoT Agents.

More information: https://fiware-idm.readthedocs.io/en/latest/

35 questions
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

Authzforce - Existing GUI for policy administration (PAP)

I just started experiment with Authzforce Fiware following the docs. I made some RBAC scenarios following the examples given, using the RESTful interface provided. What I would like to know, is whether any User Interface to manage the Policy…
NickAth
  • 1,089
  • 1
  • 14
  • 35
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
1 answer

WSo2 API Manager and Keyrock - issue with roles

I have deployed WSo2 API Manager 4.1.0 on a Debian 10 machine using the ZIP archive. I have configured my Keyrock instance as an external identity provider in the Management Console. When I log in with the Keyrock admin account, I can access the…
1
vote
1 answer

Get a list of all resources accessible to users in FIWARE

I would like to adopt FIWARE as part of our IoT platform. In addition to Orion Context Broker, I would like to use keyrock / wilma / AuthzForce for authentication and authorization. I understood by reading "step-by-step" and other documents that…
Shohei
  • 11
  • 1
1
vote
1 answer

How to provision a Dockerized secure IoT Agent with Keyrock?

I'm failing to find this information within the existing documentation - either permanent or non-permanent tokens. Using Keyrock 7.8, Ultralight 1.11.0 (though any current agent will do) The following Docker parameters are set: -…
Jason Fox
  • 5,115
  • 1
  • 15
  • 34
1
vote
1 answer

Unexplainable 403 error "User not allow to perform the action" in Keyrock

I've been struggling for a while with this issue and wondered if anyone else had the same problem. I've got a Keyrock 7.8.0 + MySQL architecture running with docker as FIWARE tutorials suggest. I can access both GUI and API through localhost:3005.…
Mannix
  • 41
  • 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
0 answers

Not able to Login in keyrock IDM using Nginx

I have installed nginx reverse proxy server and fiware keyrock IDM. I want to access fiware keyrock using Nginx server with the url https://"nginx-ip"/key My nginx conf is as follows: location /idm/ { proxy_set_header X-Forwarded-Host …
Timshrok
  • 97
  • 1
  • 1
  • 12
1
vote
0 answers

Token expiration from FIWARE Keyrock using oauth2

In FIWARE Keyrock, using oauth2, how to I change the duration of the tokens from the default 3600 seconds? I tried to change keystone.conf - [token] - expiration, with no success. I already get the information that oauth2 is not original from…
0
votes
0 answers

Kong-keyrock Authorize issue with Query parameter (type)

I tried to use the Kong image (0.5.3) and install kong successfully and was able to connect with Keyrock Why am i not able to give Query paramter : type as a filter in keyrock permission so that user with specific permission entity type can only…
0
votes
0 answers

FIWARE Keyrock identity management

I use the FIWARE IdM to protect an Orion Context Broker. After upgrading FIWARE IDM to the latest version the following POST request, which worked fine in the past, does not work anymore. Does anybody know what the error message means and how to fix…
gasp
  • 23
  • 3
0
votes
1 answer

I can't get X-Auth-Token from keyrock

I am making a project for uni. I'm making the following request directly to keyrock using .http to get the default admin's X-Auth-Token: POST http://localhost:3005/v1/auth/tokens Content-Type:…
1
2 3