Multiple JITP CA per product about nerves_hub_web HOT 4 CLOSED

The relation is the other way. @jjcarstens can comment on that line. However, it should be many CAs to one product.

A CA can only JITP for one product, though. You can't have one CA JITP'ing for multiple products since NH wouldn't know which product to assign to the device when it first authenticates.

from nerves_hub_web.

I understand a CA can only JITP for one product.
I may be wrong, but on line 12, create unique_index(:jitp, [:product_id]) enforces a single JITP enabled CA per product.
From https://github.com/nerves-hub/nerves_hub_web/blob/main/apps/nerves_hub_web_core/lib/nerves_hub_web_core/products/product.ex#L22 , we have in Product : has_one :jitp

@jjcarstens can you explain this limitation ?

from nerves_hub_web.

Right now there is a hard limitation of one JITP CA per product because of that unique index (as @jeanparpaillon said). But we should probably remove that so unique index so that many CAs can JITP one product (as @fhunleth said). The way CAs are structured already enforces that a CA can only JITP for one product

FWIW, we had discussed this need for our internal instance, but then moved away from using JITP entirely and hadn't circled back to it. I believe we can simply just remove the linked index for :product_id on JITP records

from nerves_hub_web.

Got it. I forgot the discussion and just assumed that it was working for us internally at one time. The restriction doesn't make sense, and if it's as simple as removing the linked index for :product_id, then I'm definitely for it.

from nerves_hub_web.