-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set up server nodes on AWS #6
Comments
Hi @slamora, I've sent a status update to your email. Basically, you can start testing your integration. Please let me know if you still have any questions. |
Hi @ksbomj , We've succesful deployed the client-helper-application, but we don't know how to configure Authentication. How should we proceed? FYI, when we run the getting started code of the Python client we get this response: Exception when calling ObitApi->download_obit_from_chain: (401)
Reason: Unauthorized
HTTP response headers: HTTPHeaderDict({'Server': 'nginx', 'Content-Type': 'application/json', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'X-Powered-By': 'PHP/8.0.3', 'Cache-Control': 'no-cache, private', 'Date': 'Mon, 22 Mar 2021 10:31:17 GMT', 'X-RateLimit-Limit': '60', 'X-RateLimit-Remaining': '59', 'Access-Control-Allow-Origin': '*'})
HTTP response body: {"status":1,"errorMessage":"[401] Client error: `GET https:\/\/usody.node.obada.io\/obits\/did%3Aobada%3Afe096095-e0f0-4918-9607-6567bd5756b5` resulted in a `401 Unauthorized` response:\nUnauthorized\n"}
--Call-- Thanks. |
Latest update, I've understood that our node deployed on AWS is configured using Basic Auth. How can we configure Basic Auth on |
I wonder about the status of the set up of the server nodes on AWS . How is it going? Thanks!
The text was updated successfully, but these errors were encountered: