Skip to content
Documentation Menu

Authorize

Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.1 (Messages); Functional Block C. Authorization

Overview

The Charging Station sends AuthorizeRequest to the CSMS to obtain authorization for an idToken before starting (or stopping) a transaction. OCPP 2.0.1 also supports authorization of EV Contract Certificates (ISO 15118): the CS may include the EV's PEM-encoded certificate chain and OCSP request data so that the CSMS / CA can validate the contract certificate.

The CSMS replies with AuthorizeResponse containing the idTokenInfo (status, expiry, groupId) and, when applicable, a certificateStatus.

The Charging Station MAY skip Authorize and rely on its Local Authorization List or Authorization Cache (use cases C10–C14) for an offline/local decision.

Sequence Diagram

Charging Station  ──── AuthorizeRequest ────▶  CSMS
                       (idToken, certificate?, iso15118CertificateHashData?)
Charging Station  ◀─── AuthorizeResponse ────  CSMS
                       (idTokenInfo, certificateStatus?)

Initiator

Charging Station → CSMS

Fields

Field NameField TypeCard.Description
idTokenIdTokenType1..1Required. The identifier that needs to be authorized.
certificatestring [0..5500]0..1Optional. The X.509 certificate chain presented by the EV, PEM-encoded. Order is from leaf up to (but excluding) root.
iso15118CertificateHashDataOCSPRequestDataType0..4Optional. Information needed to verify the EV Contract Certificate via OCSP.

AuthorizationStatusEnumType (carried inside idTokenInfo.status)

Accepted, Blocked, ConcurrentTx, Expired, Invalid, NoCredit, NotAllowedTypeEVSE, NotAtThisLocation, NotAtThisTime, Unknown.

Examples

{
  "idToken": {
    "idToken": "044943121F1A80",
    "type": "ISO14443"
  }
}

Schema

Source: schemas/AuthorizeRequest.json, schemas/AuthorizeResponse.json (OCPP 2.0.1 FINAL)

Request schema (JSON Schema)
Response schema (JSON Schema)