TC_C_45_CS — Authorization by GroupId - Master pass - Not able to start transaction + groupId
TC_C_45_CS — Authorization by GroupId - Master pass - Not able to start transaction + groupId
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block C. Authorization, page 115.
Identification
| Field | Value |
|---|---|
| Test case name | Authorization by GroupId - Master pass - Not able to start transaction + groupId |
| Test case Id | TC_C_45_CS |
| Use case Id(s) | C09 |
| Requirement(s) | C16.FR.03 |
| System under test | Charging Station |
| Functional block | C. Authorization |
Description
This test case covers how a Charging Station can authorize an action for an EV Driver based on GroupId information. This could for example be used if 2 people regularly use the same EV: they can use their own IdToken (e.g. RFID card), and can deauthorize transactions that were started with the other idToken (with the same GroupId).
Purpose
To verify if the Charging Station is able to correctly handle the Authorization of an idToken with the same GroupId as the MasterPassGroupId according to the mechanism as described in the OCPP specification.
Prerequisite(s)
- The Charging station supports MasterPass feature.
Before (Preparations)
Configuration State:
- TxCtrlr.TxStartPoint should contain Authorized or PowerPathClosed and not contain ParkingBayOccupancy or EVConnected AuthCtrlr.MasterPassGroupId is <Configured MasterPassGroupId>
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Manual Action: Present configured masterpass idToken | |
| 1. The Charging Station sends an AuthorizeRequest | 2. The OCTT responds with an AuthorizeResponse with; - idTokenInfo.status Accepted; - idTokenInfo.groupIdToken.idToken <Configured masterPassGroupId> |
| Note: The Charging Station will not authorize the transaction and send a TransactionEventRequest (in case of TxStartPoint Authorized). | |
| 3. Execute Reusable State EVConnectedPreSession | |
| 4. The Charging Station will NOT send a TransactionEventRequest with chargingState Charging and triggerReason ChargingStateChanged |
Tool validations
Step 1:
Message AuthorizeRequest
- idToken.idToken <Configured valid_idtoken_idtoken>
- idToken.type <Configured valid_idtoken_type>
Post scenario validations
- N/a