Documentation Menu

TC_C_09_CS — Authorization through authorization cache - Invalid & Not Accepted

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

Identification

Field	Value
Test case name	Authorization through authorization cache - Invalid & Not Accepted
Test case Id	TC_C_09_CS
Use case Id(s)	C12
Requirement(s)	C12_FR_05, C10_FR_03
System under test	Charging Station
Functional block	C. Authorization

Description

This test case describes how the EV Driver is authorized to start a transaction while the Charging Station uses Cached IdToken. This enables the EV Driver to Online start a transaction by using the Authorization Cache in which the Charging Station can respond faster, as no AuthorizeRequest is being sent.

Purpose

To verify if the Charging Station is able to Authorize an idToken which has status "Invalid" in its cache according to the mechanism as described in the OCPP specification.

Prerequisite(s)

AuthCacheCtrlr.AuthCacheAvailable is implemented with value true

Before (Preparations)

Configuration State:

AuthCacheCtrlr.AuthCacheEnabled is true (If implemented) AuthCtrlr.LocalPreAuthorize is true (If implemented) AuthCacheCtrlrDisablePostAuthorize is false (If implemented)

Memory State:

IdTokenCached for <Configured invalid IdToken fields>

Reusable State(s):

State is EVConnectedPreSession

Main (Test scenario)

Charging Station	CSMS
Manual Action: Present Invalid idToken which is already configured in the Authorization Cache
1. The Charging Station sends a AuthorizeRequest	2. The OCTT responds with a AuthorizeResponse with idTokenInfo.status Invalid

Tool validations

Step 1:

Message AuthorizeRequest

idToken.idToken <Configured invalid_idtoken_idtoken>
idToken.type <Configured invalid_idtoken_type>

TC_C_09_CS — Authorization through authorization cache - Invalid & Not Accepted