Hey @Colleen , I thought of another topic that would unlock the next “level” for me: OAuth.
OAuth by itself is vague and needs an application. Perhaps the topic is better described as secure identification and communication.
It all started when I wanted to make a mobile app to see the status of my device (sump water level monitor).
In order to communicate with an Argon I need to hide its access token within the mobile app. That’s when I started down the OAuth rabbit hole, which turned into a Firebase rabbit hole… I haven’t come out yet. This presentation was really helpful. Now I understand what has to be done, but still learning how to do it in the Particle echo system.
I read the Authentication tutorial, but it seems daunting to implement. The Authenticating chapter is also informative. I am getting lost in the layers of the onion: Product, Customer, Clients, IDs, Tokens, Keys, App, etc.
I see the note in the docs saying that code examples will be added. Do you know if there is active work on this?
I would like a tutorial that goes from start to finish. Create a product, customers, clients, scopes, etc, and any difference in behavior between a Product token and a Developer.
Then, show how to put it all together with code that reads variables and calls functions.
It seems there is more to do to setup the Particle device than there is to write the code.