Re: Implementation of ClearCache and AuthorizationCache functionalities #428

Activity

1. matth-x commented on Nov 11, 2025

   

   matth-x

   on Nov 11, 2025

   Owner

   More actions

   AuthorizationCache is currently not supported, only LocalAuthLists.

   To implement it, you need to implement NFC based authorization in firmware. Then you can build a list of known idTags. After NFC swipe, check if the idTag exists in the list and still valid, and if not, send an Authorize request like here:

   MicroOcpp/src/MicroOcpp/Model/ConnectorBase/Connector.cpp

   Lines 789 to 801 in da3428a

   	auto authorize = makeRequest(new Ocpp16::Authorize(context.getModel(), idTag));
   	authorize->setTimeout(authorizationTimeoutInt && authorizationTimeoutInt->getInt() > 0 ? authorizationTimeoutInt->getInt() * 1000UL : 20UL * 1000UL);
   	if (!context.getConnection().isConnected()) {
   	//WebSockt unconnected. Enter offline mode immediately
   	authorize->setTimeout(1);
   	}
   	auto tx = transaction;
   	authorize->setOnReceiveConfListener([this, tx] (JsonObject response) {
   	JsonObject idTagInfo = response["idTagInfo"];
   	if (strcmp("Accepted", idTagInfo["status"] | "UNDEFINED")) {

   The Authorization confirmation handler needs to contain the logic to update the local cache and to initiate the transaction if all looks good using beginTransaction_authorized(...)

   The ClearCache command needs to be overridden in the firmware. There are plenty of examples in the unit tests, in general it looks like this:

   MicroOcpp/tests/Reset.cpp

   Lines 53 to 62 in da3428a

   	getOcppContext()->getOperationRegistry().registerOperation("TransactionEvent", [] () {
   	return new Ocpp16::CustomOperation("TransactionEvent",
   	[] (JsonObject) {}, //ignore req
   	[] () {
   	//create conf
   	auto doc = makeJsonDoc("UnitTests", 2 * JSON_OBJECT_SIZE(1));
   	auto payload = doc->to<JsonObject>();
   	payload["idTokenInfo"]["status"] = "Accepted";
   	return doc;
   	});});

   To check for the OCPP Configurations, use the Configuation API for existing Configurations:

   MicroOcpp/src/MicroOcpp/Core/Configuration.h

   Line 29 in da3428a

   Configuration *getConfigurationPublic(const char *key);

   Or if you need to add new Configurations:

   MicroOcpp/src/MicroOcpp/Core/Configuration.h

   Line 22 in da3428a

   std::shared_ptr<Configuration> declareConfiguration(const char *key, T factoryDefault, const char *filename = CONFIGURATION_FN, bool readonly = false, bool rebootRequired = false, bool accessible = true);

   There are a few examples in the MicroOCPP source code about Configurations. I would recommend searching for similar functionality in the source, and then copy and paste the necessary to the outer firmware integration.