All stories
PharmaFaable Auth

Process data from the PLC to the cloud, every reading attributable

Each gateway proves who it is with a key that never leaves it, gets one permission for one API, and leaves a trail of every token it ever asked for.

0shared secrets on the plant floor

Illustrative scenario based on patterns we see across teams building on Faable.

A gloved hand operating equipment in a pharmaceutical clean room
Photo: Mina Rad on Unsplash

The team

A European pharmaceutical plant with several packaging lines monitored by PLCs. Its automation and IT teams stream process data (temperatures, pressures, line speeds, vision rejects) to an analytics platform in a public cloud.

The challenge

In a GMP environment, data you can't attribute is data you can't use. Every reading had to reach the cloud from the right gateway, attributed to the right line, with no credential that someone could copy from a backup and replay. Machines and people also needed different rights: line gateways write telemetry, the MES gateway writes batch records, QA reviews and approves, and auditors only read.

How they built it

  1. 1

    A private-key identity per gateway

    Each Node-RED gateway next to a PLC is its own machine client, authenticated with a private key generated on the gateway (private_key_jwt). Faable stores only the public half, so no flow export or backup contains a secret.

  2. 2

    One API per capability

    Telemetry and batch records are separate APIs, each with a single permission. A telemetry token is bound to the telemetry API by its audience, and every other API rejects it.

  3. 3

    Only registered gateways, stamped with their line

    A client-credentials Action lets only registered gateways get a token and adds the plant and line to it. The platform reads where each reading came from in a signed claim, never in the payload.

  4. 4

    Roles for people

    Operators read telemetry. QA reviewers also read and approve batch records, and auditors get read-only access. Roles decide what each person's token carries.

  5. 5

    A trail of every token

    The tenant logs record every token issued and every failed attempt, per gateway, with the source IP and the reason. Cutting off a lost gateway means deleting its client.

The result

No shared secrets on the plant floor, and every reading attributable to a gateway and a line. Every token issued and every failed attempt is logged, and cutting off a lost gateway takes one action without touching the others.

Add auth in minutes

Create a tenant, drop in the SDK, and ship passwordless, social and M2M auth — hosted in the EU, GDPR by default. Free to start, no credit card required.