TC_C_20_CSMS — Authorization through authorization cache - Invalid
TC_C_20_CSMS — Authorization through authorization cache - Invalid
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 369.
Identification
| Field | Value |
|---|---|
| Test case name | Authorization through authorization cache - Invalid |
| Test case Id | TC_C_20_CSMS |
| Use case Id(s) | C12 |
| Requirement(s) | C12_FR_03 |
| System under test | CSMS |
| 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 CSMS is able to respond correctly when an idToken, which has status "Invalid" in the charging stations cache but not in the CSMS, is presented according to the mechanism as described in the OCPP specification.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT sends a TransactionEventRequest with; - triggerReason Authorized; - idToken.idToken <Configured invalid_idtoken_idtoken>; - idToken.type <Configured invalid_idtoken_type> - eventType Updated; Note(s):; - TxStartPoint contains ParkingBayOccupancy | 2. The CSMS responds with a TransactionEventResponse |
Tool validations
Step 2:
Message TransactionEventResponse
- idTokenInfo.status Invalid or Unknown
Post scenario validations
- N/a