From 95b4647a2241edf21ecb72e035c1f08fe927d78e Mon Sep 17 00:00:00 2001 From: Troy McConaghy Date: Sat, 3 Mar 2018 19:15:01 +0100 Subject: [PATCH] Added instructions for including secret token header in POST requests --- .../source/production-deployment-template/workflow.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/server/source/production-deployment-template/workflow.rst b/docs/server/source/production-deployment-template/workflow.rst index b60a5d7f..3bba5c05 100644 --- a/docs/server/source/production-deployment-template/workflow.rst +++ b/docs/server/source/production-deployment-template/workflow.rst @@ -105,6 +105,12 @@ You can make up that ``SECRET_TOKEN`` now. For example, ``superSECRET_token4-POST*requests``. You will put it in the ``vars`` file later. Every BigchainDB node in a cluster can have a different secret token. +To make an HTTP POST request to your BigchainDB node, +you must include an HTTP header named ``X-Secret-Access-Token`` +and set it equal to your secret token, e.g. + +``X-Secret-Access-Token: superSECRET_token4-POST*requests`` + 3. Deploy a Kubernetes cluster for your BigchainDB node. We have some instructions for how to :doc:`Deploy a Kubernetes cluster on Azure <../production-deployment-template/template-kubernetes-azure>`.