Skip to content
Documentation Menu

TC_C_38_CS — Clear Authorization Data in Authorization Cache - Rejected

TC_C_38_CS — Clear Authorization Data in Authorization Cache - Rejected

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 107.

Identification

FieldValue
Test case nameClear Authorization Data in Authorization Cache - Rejected
Test case IdTC_C_38_CS
Use case Id(s)C11
Requirement(s)C11_FR_01, C11.FR.02, C11.FR.04
System under testCharging Station
Functional blockC. Authorization

Description

This test case covers how the Charging Station autonomously stores a record of previously presented identifiers that have been successfully authorized by the CSMS in the Authorization Cache. (Successfully meaning: a response received on a message containing an IdToken)

Purpose

To verify if the Charging Station is able to correctly respond on a request from the CSMS to clear all identifiers from the Authorization Cache while the feature is disabled according to the mechanism as described in the OCPP specification.

Prerequisite(s)

  • AuthCacheCtrlr.AuthCacheAvailable is implemented with value true
  • AuthCacheCtrlr.LocalPreAuthorize is implemented

Before (Preparations)

Configuration State:

  • AuthCacheEnabled is false (If implemented)

Memory State:

  • IdTokenCached for <Configured valid IdToken fields>

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
2. The Charging Station responds with a ClearCacheResponse1. The OCTT sends a ClearCacheRequest

Tool validations

Step 2:

Message ClearCacheResponse

  • status Rejected

Post scenario validations

  • N/a