@jeiden & @brycekahle
I’ve posted this question on a few other threads, but moved it here because I think it deserves it’s own topic.
We’re migrating to Particle’s recommended two-legged authentication. Until now, we’ve been managing our own user accounts/authentication and communicating with Particle exclusively through our server. i.e.
our users -> our mobile/web app -> our server -> Particle
Our server is currently using a single “never-expiring-token” to communicate with Particle, and make all device calls. We have DB tables associating our users with the devices they own, and “scope” control for a given user in that way. With this configuration, all of our devices (most assigned to our Particle product id, some generic photons) are owned/claimed by a single user on our team’s Particle account. We have not yet created Particle customers.
As I migrate to two-legged auth, I will create a Particle customer + scoped token + claim code via our app when our users create an account with us and bring our device online for the first time. But I need to circle back to the devices already in the field. I want to write a script to retroactively create Particle customers for all the users in my db, then associate their devices and use properly scoped tokens. How can I do that? I tried unclaiming a device, then reclaiming using a customer scoped token… but no success. The device seems to have moved beyond my visibility/control entirely.
Is there a way to remotely transfer ownership/claim of a device to a customer? Asking all my users to go through the SoftAP process again (i.e. bringing the device back online with a new claim code) would be really inconvenient.