Authorize rejected — invalid idTag

How it presents

Symptom

Authorize rejected — invalid idTag — badge/app presents locally but CSMS returns Invalid/Blocked, or local list is stale after prolonged offline. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F03.

Root causes (by observed frequency)

1. #1 idTag not in CSMS allowlist / expired membership

   Reader may be fine

2. #2 Local authorization list empty after long offline
3. #3 Wrong parentIdTag / group mapping after fleet change
4. #4 Clock skew making token windows fail

Diagnostic procedure

1. 1. Capture Authorize.conf status and idTag (scrub PII beyond need)

   Expected: Invalid vs ConcurrentTx

   Tools: CSMS

2. 2. Compare same badge on a known-good stall

   Expected: Sitewide vs one stall

   Tools: badge

3. 3. Check local auth list / offline policy on the charger

   Expected: List present if required

   Tools: HMI

4. 4. Verify station clock vs NTP/CSMS time

   Expected: Skew within policy

   Tools: HMI, CSMS

5. 5. Have CSMS admin repair allowlist/group mapping

   Tools: CSMS admin

The fix

Authorize Invalid is almost always CSMS/list/clock — prove before reader RMA.

1. Do not replace RFID hardware for a clean Invalid Authorize.
2. Repair CSMS allowlist or fleet group mapping. Document readings and scrubbed photos for OCPP-F03 before closing the ticket.
3. Refresh local authorization cache after reconnect. Document readings and scrubbed photos for OCPP-F03 before closing the ticket.
4. Correct clock/NTP if token windows are failing. Document readings and scrubbed photos for OCPP-F03 before closing the ticket.
5. Retest badge and document Authorize.conf for confirmations.