RFID & Authentication

Q: What is the standard RFID authentication flow in eMabler?
A: When an RFID tag is presented, the charger sends an Authorize message via OCPP. eMabler checks the tag against:

1. Local driver registry (eMabler database)

2. Real-time auth (custom or generic push integration)

3. OCPI fallback (if enabled)
   If accepted, the charger transitions to Preparing state and starts the session.

Q: Why does an RFID tag fail to authenticate?
A: Common reasons include:

• Tag not registered or expired

• Assigned user disabled or lacks permission

• Real-time auth timeout or rejection

• OCPI partner credentials misconfigured

Q: Can the same RFID tag be used across multiple services?
A: Yes. If configured properly, one tag can be assigned to users across multiple tenants or organizations. Permissions are scoped per organization.

Q: What’s the difference between generic and custom real-time auth?
A:

• Generic RealTimeAuth: Configured via Connect, applies to all chargers, and falls back to OCPI on failure.

• Custom Push Integration: Requires explicit integrationRelays setup and does not fallback to OCPI unless custom logic allows it.

Q: What happens if both generic and custom real-time auth are active?
A: This causes conflicts and unreliable behavior. eMabler recommends disabling one. Generic RealTimeAuth can be disabled via Connect → More → Settings → Developers.

Q: Can I reject a tag via real-time auth and trigger fallback to OCPI?
A: Yes. If your real-time webhook responds with "charging_allowed": false and reason "UNKNOWN_RFID_TAG_ID", eMabler will then attempt to validate the tag via OCPI.