TC_C_17_CS — Authorization through authorization cache - StopTxOnInvalidId = false
TC_C_17_CS — Authorization through authorization cache - StopTxOnInvalidId = false
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 98.
Identification
| Field | Value |
|---|---|
| Test case name | Authorization through authorization cache - StopTxOnInvalidId = false |
| Test case Id | TC_C_17_CS |
| Use case Id(s) | C12 |
| Requirement(s) | C12_FR_02, C12_FR_04 |
| 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 respond correctly to an idToken which has status "Accepted" in its cache but is "Invalid" in the CSMS when StopTxOnInvalidId is false according to the mechanism as described in the OCPP specification.
Prerequisite(s)
- AuthCacheCtrlr.AuthCacheAvailable is implemented with value true
- At least one of the following must be supported; Local auth list, auth cache, StartTxUnknownIds.
Before (Preparations)
Configuration State:
- AuthCacheEnabled is true (If implemented) LocalPreAuthorize is true (If implemented) OfflineTxForUnknownIdEnabled is true (If implemented) StopTxOnInvalidId is false MaxEnergyOnInvalidId is 0
Memory State:
- IdTokenCached for <Configured valid IdToken fields> (If implemented) A known valid idToken is configured in the Local auth list (if implemented) and auth cache (if implemented)
Reusable State(s):
- State is EVConnectedPreSession
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 1. The OCTT closes the WebSocket connection AND does not accept a reconnect. | |
| Manual Action: Present valid idToken which is already configured in the Authorization Cache | |
| Note(s): The OCTT will wait for 5 seconds | |
| 2. The OCTT accepts reconnection attempt from the Charging Station. | |
| Note(s):; - The Charging Station will empty its Transaction message queue. This will contain one or more TransactionEventRequest messages | |
| 3. The Charging Station sends a TransactionEventRequest | 4. The OCTT responds with a TransactionEventResponse with idTokenInfo.status Invalid (if idToken is not omitted) |
| 5. The Charging Station sends a TransactionEventRequest with triggerReason SuspendedEVSE | 6. The OCTT responds with a TransactionEventResponse |
Tool validations
Step 2:
Message TransactionEventRequest A message with:
- triggerReason Authorized
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
- offline True A message with:
- transactionInfo.chargingState SuspendedEVSE No message with: - triggerReason SuspendedEVSE
Post scenario validations
- Energyflow stops on receiving status invalid