From f2dcc347e576dc30ca1ac750a1c9d341a3d41dd5 Mon Sep 17 00:00:00 2001 From: Merlin Carter Date: Thu, 5 Sep 2019 15:42:59 +0200 Subject: OTA-3682: Remove the existing doc Removing the existing meta-updater doc so it can be moved into the aktualizr repo. Also updated README to point to same files in aktualizr repo. Signed-off-by: Merlin Carter --- docs/modules/ROOT/pages/provisioning-methods.adoc | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 docs/modules/ROOT/pages/provisioning-methods.adoc (limited to 'docs/modules/ROOT/pages/provisioning-methods.adoc') diff --git a/docs/modules/ROOT/pages/provisioning-methods.adoc b/docs/modules/ROOT/pages/provisioning-methods.adoc deleted file mode 100644 index 0f9051e..0000000 --- a/docs/modules/ROOT/pages/provisioning-methods.adoc +++ /dev/null @@ -1,22 +0,0 @@ -= Manual provisioning - -//MC: TOMERGE: Looks mostly like a duplicate of this topic: https://github.com/advancedtelematic/aktualizr/blob/master/docs/ota-client-guide/modules/ROOT/pages/simulate-device-cred-provtest.adoc - -As described in the xref:xref:dev@ota-build::sota-variables.adoc[configuration reference], you can set `SOTA_DEPLOY_CREDENTIALS` to `0` to prevent deploying credentials to the built `wic` image. In this case you get a generic image that you can use e.g. on a production line to flash a series of devices. The cost of this approach is that this image is half-baked and should be provisioned before it can connect to the backend. - -Provisioning procedure depends on your provisioning recipe, i.e. the value of `SOTA_CLIENT_PROV` (equal to `aktualizr-shared-prov` by default): - -* For `aktualizr-shared-prov` put your `credentials.zip` to `/var/sota/sota_provisioning_credentials.zip` on the filesystem of a running device. If you have the filesystem of our device mounted to your build machine, prefix all paths with `/ostree/deploy/poky` as in `/ostree/deploy/poky/var/sota/sota_provisioning_credentials.zip`. -* For `aktualizr-device-prov` -** put URL to the backend server (together with protocol prefix and port number) at `/var/sota/gateway.url`. If you're using HERE OTA Connect, you can find the URL in the `autoprov.url` file in your credentials archive. -** put client certificate, private key and root CA certificate (for the *server*, not for the *device*) at `/var/sota/import/client.pem`, `/var/sota/import/pkey.pem` and `/var/sota/import/root.crt` respectively. -* For `aktualizr-device-prov-hsm` -** put URL to the server backend (together with protocol prefix and port number) at `/var/sota/gateway.url`. If you're using HERE OTA Connect, you can find the URL in the `autoprov.url` file in your credentials archive. -** put root CA certificate (for the *server*, not for the *device*) at `/var/sota/import/root.crt`. -** put client certificate and private key to slots 1 and 2 of the PKCS#11-compatible device. - -For more extensive information on provisioning methods, see the following topics from the OTA Connect Developer guide: - -//MC: Web links because this topic is only viewable in Github -* link:https://docs.ota.here.com/ota-client/dev/client-provisioning-methods.html[Device provisioning methods] -* link:https://docs.ota.here.com/ota-client/dev/enable-device-cred-provisioning.html[Enable device-credential provisioning and install device certificates] -- cgit v1.2.3-54-g00ecf