Skip to content

Latest commit

 

History

History
80 lines (57 loc) · 2.86 KB

keystone.md

File metadata and controls

80 lines (57 loc) · 2.86 KB

NGSI Go tutorial for IDM Keystone

Introduction

NGSI Go supports Keystone (part of the OpenStack project) as IDM. More in detail, the security framework in this case is:

Note this is the stack used by ThinkingCities platform.

This tutorial describes how to use NGSI Go in this scenario.

Preconditions

  • Orion PEP is running at endpoint http://orion-pep:1026
  • Keystone IDM is running at endpoint http://idm:5001
  • A service named smartgondor is created in Keystone IDM
  • A subservice named /irrigation is created within service smartgondor
  • A subservice named /watermeter is created within service smartgondor
  • The user admin_smartgondor with password admin1234 has permissions on /irrigation and /watermetersubservices

If you are unfamiliar with the service and subservice concepts this reference can be useful.

Using subservice in the IDM configuration

Create the broker using the following command:

ngsi broker add \
  --host mybroker \
  --ngsiType v2 \
  --brokerHost http://orion-pep:1026 \
  --idmType ThinkingCities \
  --idmHost http://idm:5001/v3/auth/tokens \
  --username admin_smartgondor \
  --password admin1234 \
  --service smartgondor \
  --path /irrigation

You can now use the mybroker broker to do any NGSIv2 operation. For instance, to create an entity in the /irrigation subservice:

ngsi create --host mybroker entity --data '{"id":"E", "type": "T", "A": {"value": 1, "type": "Number"}}'

The key point is that NGSI Go will deal transparently with all security aspects (i.e. get a token from IDM, renew token when it expires, etc.) for the user.

More detail on NGSIv2 operations in this side tutorial.

Not using subservice in the IDM configuration

As alternative, you can omit --path parameter in the ngsi broker add command. This way:

ngsi broker add \
  --host mybroker \
  --ngsiType v2 \
  --brokerHost http://orion-pep:1026 \
  --idmType ThinkingCities \
  --idmHost http://idm:5001/v3/auth/tokens \
  --username admin_smartgondor \
  --password admin1234 \
  --service smartgondor \

This allow you to use the same broker specification (mybroker) for several subservices, eg:

ngsi create --host mybroker --path /irrigation entity --data '{"id":"E", "type": "T", "A": {"value": 1, "type": "Number"}}'


ngsi create --host mybroker --path /watermeter entity --data '{"id":"E", "type": "T", "A": {"value": 1, "type": "Number"}}'

If you don't specify --path then / is used as default.