along with removing the provisioning code
and simplifying the cert key auth configurator
oh, and also move the 'workflow' section to the cli docs, as they are cli specific
In short, the top tier of security and 'connecting your device to NervesHub` is to use a crypto chip (NervesKey). NervesKey is the 'production grade' deployment setup. If you aren't using NervesKey, then using Shared Secret auth is probably the next option to consider as your device isn't likely out in the field yet.
This is based on some discussions I had with @jjcarstens today.
along with removing the provisioning code and simplifying the cert key auth configurator oh, and also move the 'workflow' section to the cli docs, as they are cli specific
In short, the top tier of security and 'connecting your device to NervesHub` is to use a crypto chip (NervesKey). NervesKey is the 'production grade' deployment setup. If you aren't using NervesKey, then using Shared Secret auth is probably the next option to consider as your device isn't likely out in the field yet.
This is based on some discussions I had with @jjcarstens today.