TC_073_CSMS — Update Charge Point Password for HTTP Basic Authentication
TC_073_CSMS — Update Charge Point Password for HTTP Basic Authentication
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 180.
Identification
| Field | Value |
|---|---|
| Test case name | Update Charge Point Password for HTTP Basic Authentication |
| Test case Id | TC_073_CSMS |
| System under test | Central System |
Description
The Central System can configure a new password for HTTP Basic Authentication, the Central System can send a new value for the BasicAuthPassword Configuration key.
Purpose
To check if the Central System is able to change the Basic Authentication password.
Prerequisite(s)
The Central System supports Security profile 1 and/or 2.
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- N/a
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| Manual Action: Update the basic authentication password | |
| 2. The Charge Point responds with a ChangeConfiguration.conf | 1. The Central System sends a ChangeConfiguration.req |
| 3. The Charge Point disconnects its current connection and reconnects to the Central System using the provided password from step 1. |
Tool validation(s)
Charge Point side:
Step 2:
(Message: ChangeConfiguration.conf) status is Accepted
Central System side:
Step 1:
(Message: ChangeConfiguration.req) key is AuthorizationKey value contains the hex encoded representation of the basic authentication password the Charge point needs to use when connecting to the Central System. Because it is advised to use a randomly generated binary to get maximal entropy, the tool only validates if the new password adheres to the OCPP password requirements:
- The hexadecimal representation of the password has a maximum of 40 characters.
- The length of the password must be between 16 and 20 bytes.
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a