Sep 05 2018
- last edited on
May 26 2021
Dear Blockchain gurus,
We followed below link to create Azure Blockchain workbench infrastructure.
Created default sample application following steps as mentioned.
Granted permissions as mentioned on above links. However as mentioned by Microsoft about APIs on following link: https://docs.microsoft.com/en-us/azure/blockchain-workbench/blockchain-workbench-use-api giving us 401 error.
We try to use built-in swagger URL but no luck as well as following examples of AUTH. https://github.com/Azure-Samples/blockchain & https://github.com/Azure-Samples/blockchain/blob/master/blockchain-workbench/rest-api-samples/dotnet...
But no luck so far to after getting authentication token but workbench gateway API is unaccusable.
We would suggest to create your own workbench application following above steps which will not take more than 2 hours and try to access API using swagger. Otherwise we can share with you our subscription and deployment details.
Please find attached, which have 401 authorization error’s source code (Client Code).
Please let me know if conference call is needed to explain further.
Sep 05 2018 05:11 PM
Sep 21 2018 07:57 AM
Documentation appears incomplete for https://github.com/Azure-Samples/blockchain/tree/master/blockchain-workbench/auth-samples.
Its states: Navigate to this directory and run the following commands:
npm install npm start
What directory is it referring to? It does the same statement for the Option 2 Docker install. Thanks.
Sep 24 2018 12:55 PM
Sep 24 2018 11:35 PM - edited Sep 24 2018 11:42 PM
Thank you so much for you kind replies. We are able to sort out this issue by our own previous experience with APIs management in Azure.
Someone from Microsoft on the issue we faced and he informed us that the failure we experienced was most likely caused by the instance type we selected (We went with a D-Series Low End VM last time), the current deployment is running an F-Series Instance (Optimized for CPU Performance) as he indicated that Blockchain is CPU intensive and should have an F Series VM.
Oct 13 2018 10:53 PM
Could you please share how you solved your problem as I am getting the same issue. I have ensured that the bearer token is obtained and used but keep getting error 401.
Thanks in advance!
Oct 14 2018 12:12 AM
Please find the complete fix on this blog URL, that i just published.
Oct 16 2018 12:07 AM