Tokens

Token Object

Tokens are security keys associate with an EV Driver. These are used to authenticate the driver for access to resources across the Organization such as Chargestations & Connectors.

Tokens may be of type "physical" e.g. RFID tags or "virtual" e.g. for drivers authenticating via Slack or other workplace directories.

{
	"active": true,
	"_id": "5f1031c5f5432529b37b812a",
	"physicalId": "U0146UGUH1R",
	"type": "Central",
	"organization": "5e7e6c058a6deccfefdf4223",
	"createdAt": "2020-07-16T10:53:57.764Z",
	"updatedAt": "2020-08-05T10:49:28.765Z",
	"driver": "5f1031c4f5432529b37b8129"
}

Virtual Token Example

{
	"active": true,
	"_id": "5e9d6f22dd85977168f84d63",
	"physicalId": "0D1F64DA",
	"type": "ISO14443",
	"organization": "5e7e6c058a6deccfefdf4223",
  "createdAt": "2020-07-16T10:53:57.764Z",
	"updatedAt": "2020-08-05T10:49:28.765Z",
	"driver": "5e7e727a28b1ac52051b2ef0"
}

RFID Token Example

Attributes

_id string

The Id of this token

active boolean

Use this flag to activate / deactivate this token

physicalId string

The OCPP compatible id code for this token, sent down to the CS for authentication. This has to be unique across all tokens.

type string

Tokens can be one of ['Central','ISO14443']
Central: A virtual token that only exists within eDRV
ISO14443: A physical RFID token

organization string

The Organization Id that this driver is part of
Also see Organization

createdAt datetime

Creation time of this driver's record

updatedAt datetime

Last update time of this driver's record

driver string

Each token is associated with one driver Id
Also see Driver