Skip to content
Documentation Menu

TC_C_36_CS — Store Authorization Data in the Authorization Cache - AuthCacheCtrlr.LocalPreAuthorize = false

TC_C_36_CS — Store Authorization Data in the Authorization Cache - AuthCacheCtrlr.LocalPreAuthorize = false

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

Identification

FieldValue
Test case nameStore Authorization Data in the Authorization Cache - AuthCacheCtrlr.LocalPreAuthorize = false
Test case IdTC_C_36_CS
Use case Id(s)C10
Requirement(s)C10_FR_11
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 ignore the Authorization Cache feature when LocalPreAuthorize is set to false according to the mechanism as described in the OCPP specification.

Prerequisite(s)

  • AuthCacheCtrlr.AuthCacheAvailable is implemented

Before (Preparations)

Configuration State:

  • AuthCacheEnabled is true LocalPreAuthorize is false

Memory State:

  • IdTokenCached for <Configured valid IdToken fields>

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
Manual Action: Present valid idToken which is configured in the Authorization Cache
1. The Charging Station sends an AuthorizeRequest2. The OCTT responds with an AuthorizeResponse with idTokenInfo.status Invalid

Tool validations

Step 1:

Message AuthorizeRequest

  • idToken.idToken <Configured valid_idtoken_idtoken>
  • idToken.type <Configured valid_idtoken_type>

Post scenario validations

  • N/a