Whitelisting

Intro

Learn more about whitelisting with various methods here.

What is a Whitelist?

A Whitelist is a container of identifiers used by the Charging Station for identification of EV owners to determine charging privilege.
Whitelists are set up locally or through your OCPP Backend provider.

Whitelisting through OCPP

Intro

The OCPP Whitelist is a local cache of the backend on the Charging Station.
Here, all RFIDs from authorized charge cards by the backend are transferred to the Charging Station periodically.
This is to ensure that a charging process can be authorized even if the Charging Station cannot establish a connection to the Backend. In addition, the cache allows authorization to take place much more quickly.
If this option is deactivated, a request is made to the backend every time a request is made to the Charging Station (i.e. whenever an RFID is presented to the RFID reader). Only when this is accepted, the charging process is authorized.

caution

Deactivate the OCPP Whitelist if you do not have a backend connection.

Configuration

To enable the OCPP whitelist:

1. Configure the following parameters:

Location in Dashboard	Parameter	Value	Info
AUTHORIZATION > General	Enable OCPP Whitelist	On
AUTHORIZATION > General	Enable cache	On

In the List of entries in OCPP whitelist (also List of entries in cache) then all UIDs released by the backend are cached. In which intervals this list is updated depends on the respective backend.

info

We recommend not to make any changes in this list, as they will be overwritten during the next synchronization. In certain cases, however, it may be useful to delete the entire list. To do this, remove all numbers in the list and save the change with Save & Restart.

Refreshing the OCPP Whitelist cache

In the parameter OCPP Whitelist expiry mode you can select if the Charging Station should delete entries of the cache by itself.

info

This is only used as a fallback if the Backend doesn't specify a cache-refresh period.

Location in Dashboard	Parameter	Value	Effect
AUTHORIZATION > General	OCPP Whitelist expiry mode	End of epoch 2038 (default)	(default value) the controller is configured to expire cache entries on the latest possible date (12/31/2038). In practice, this means that the local memory entries are never cleared by the controller itself. Any changes to the cache are therefore made exclusively by the backend or manually.
AUTHORIZATION > General		One year from now	The cache will automatically expire one year after the last change.

Whitelisting through the local whitelist

Overview

The local Whitelist is a backend-independent list, which is stored exclusively on the Charge Controller. UIDs which are entered in this list are always authorized for loading. There is no query to the backend.

Configuration

1. Make sure that the following parameters are set like so:

Location in Dashboard	Parameter	Value
AUTHORIZATION > General	Enable local whitelist	On
AUTHORIZATION > General	Enable fixed local list (FLL)	On

Adding RFID entries to the whitelist

add a single entry

2. Under WHITELISTS > Local Whitelist, click
3. Enter the desired UID
4. Click

import entries in bulk

2. Under WHITELISTS > Local Whitelist, click
3. Choose a CSV-file filled with IDs

The Local Whitelist should now contain the new IDs.

CSV column order

Column	Field
1	UID
2	Connector number
3	Name

CSV examples

(minimal)

839B0E0A
839B0E0B
839B0E0C

(complete)

839B0E0A,1,name
839B0E0B,2,name
839B0E0C,2,name

Scan RFID cards

2. Under WHITELISTS > Local Whitelist, click . This activates the RFID learning mode
3. Read the RFID card you'd like to add to the Whitelist through the RFID card scanner
4. Repeat step 3 for any additional cards
5. Click

The Local Whitelist should be populated with the new IDs.

---

Authorization on Double Charging Stations

Use-case: You want to authorize a UID on just one of two Charge Controllers inside a Double Charging Station.

• Add _1 to the end of a UID to authorize it only on the master Charge Controller
• Add _2 to the end of a UID to authorize it only on the slave Charge Controller

Example

UID	Effect
839B0E0A	Authorize on both Charge Controllers
839B0E0A_1	Authorize on the master Charge Controller only
839B0E0A_2	Authorize on the slave Charge Controller only