ajanikow
commented
3 years ago Hello!
Do you try to access Operator or ArangoDB endpoint? From API calls I see you to to reach ArangoDB, but endpoint and JWT token is related to Operator itself.
Once you install chart you get only Operator, after that you need to define ArangoDeployment: https://github.com/arangodb/kube-arangodb/blob/master/examples/production-cluster.yaml
It will create for you service production-cluster-ea with LoadBalancer type and production-cluster-jwt with JWT secret.
Best Regards, Adam.
tmd313
I was trying to use the API to get in via JWT. The token created in the secret: arango-kube-arangodb-1618862786-operator-token-bwdvh I took out, converted it with | base64 -d and then used that via jwtgen using the recipe described in the docs to create a superuser jwt/token. I also created the cacert by taking the ca.crt from the secret, decoding it w/base64 -d, and putting it in a cacert file. I attempted connecting via kubernetes internal network by going into another pod (I can't get any kind of shell in the current/slim arangodb pod (likely the alpine:311 is so lean) and using curl. These are what I was using in an attempt to get to the server using the new jwt I generated using the decoded token in the secret.
Or if I can find out a way I'm supposed to generate the root user password that could help too. (BTW, I don't need to nor want to obfuscate the token below, just so that you can see what it looks like.)
the myjson has only this in it (again root user password is supposed to be empty):
{ "username": "root", "password": "" }
The script did this. I get a 400/bad request on the first one and a 404 on each subsequent API call. Seems like it's not really a 404 issue though as these are basic, are they not? Script:
TOKEN="eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE2MTg5NDczODQsImV4cCI6MTYxODk1MDk4NSwiaXNzIjoiYXJhbmdvZGIiLCJzZXJ2ZXJfaWQiOiJteWNsaWVudCJ9.J1chHuzfMAkT6_xQrG_BJB9IHsCv7vbnjqLxnKVw5b4"
CACERT="/tmp/cacert"
curl -i -X POST --cacert ${CACERT} -k -H "Content-Type:application/json; charset=utf-8; Accept:application/json" -H "Authorization: Bearer ${TOKEN}" -H "Content-Length: 43" "https://arango-kube-arangodb-1618862786-operator.default.svc:8528/_open/auth -d@/tmp/myjson" curl -i -X GET --cacert ${CACERT} -k -H "Content-Type:application/json, Accept:application/json" -H "Authorization: Bearer ${TOKEN}" "https://arango-kube-arangodb-1618862786-operator.default.svc:8528/_admin/server/jwt"
curl -i -X GET --cacert ${CACERT} -k -H "Content-Type:application/json, Accept:application/json" -H "Authorization: Bearer ${TOKEN}" "https://arango-kube-arangodb-1618862786-operator.default.svc:8528/api/version"
curl -i -X GET --cacert ${CACERT} -k -H "Content-Type:application/json, Accept:application/json" -H "Authorization: Bearer ${TOKEN}" "https://arango-kube-arangodb-1618862786-operator.default.svc:8528/_api/version"
curl -i -X GET --cacert ${CACERT} -k -H "Content-Type:application/json, Accept:application/json" -H "Authorization: bearer ${TOKEN}" "https://arango-kube-arangodb-1618862786-operator.default.svc:8528/_api/query/current"
When I go to the https external endpoint:8528 (I changed it to a LoadBalancer (from the ClusterIP it originally was) and gave it an externalIP address) and all I get is a login screen with login: and password: fields but the green box on the lower right stays "grayed out" until I enter something and neither '' nor "" work as the "empty" password.
Here's the output from a run of the script above, which also contains an /api/version url w/out the _ underscore, just to try that too.
this is from within another pod in the weave network:
./queryRootUser.sh
HTTP/1.1 400 Bad Request Content-Type: text/plain; charset=utf-8 Connection: close
400 Bad RequestHTTP/1.1 404 Not Found Content-Type: text/plain Date: Wed, 21 Apr 2021 20:03:34 GMT Content-Length: 18
404 page not foundHTTP/1.1 404 Not Found Content-Type: text/plain Date: Wed, 21 Apr 2021 20:03:34 GMT Content-Length: 18
404 page not foundHTTP/1.1 404 Not Found Content-Type: text/plain Date: Wed, 21 Apr 2021 20:03:34 GMT Content-Length: 18
404 page not foundHTTP/1.1 404 Not Found Content-Type: text/plain Date: Wed, 21 Apr 2021 20:03:34 GMT Content-Length: 18
404 page not found
Please help and/or point me to reference docs that I may have missed, I've been scouring around for days on this and read the documentation over and over again.
Thanks, Tim