New user of Dgraph : "unauthorized ip address: 192.168.65.3",

Users Dgraph
1

What I want to do

Wanted to limit the access to query/mutation of schema. running Kubernetes with docker engine on mac.

What I did

Followed the steps mentioned in the following url

Configured helm file with security flag with whitelist and token. once both of them is configured unable to query the schema from my laptop.

If i remove the token flag then able to query.

Following is the configured on helm values.yaml for Dgraph alpha

Whitelist allow access

security:
#whitelist: 10.0.0.0/8,172.0.0.0/8,192.168.0.0/16
whitelist: 0.0.0.0/0,192.168.65.3/32
token:

So wondering if the token is configured in the alpha will it remove access to /admin endpoint to query

Dgraph metadata

dgraph version dgraph version

Dgraph version : v21.03.1
Dgraph codename : rocket-1
Dgraph SHA-256 : a00b73d583a720aa787171e43b4cb4dbbf75b38e522f66c9943ab2f0263007fe
Commit SHA-1 : ea1cb5f35
Commit timestamp : 2021-06-17 20:38:11 +0530
Branch : HEAD
Go version : go1.16.2
jemalloc enabled : true

For Dgraph official documentation, visit Overview - Dgraph.
For discussions about Dgraph , visit http://discuss.hypermode.com.
For fully-managed Dgraph Cloud , visit Overview - Dgraph.

Licensed variously under the Apache Public License 2.0 and Dgraph Community License.
Copyright 2015-2021 Dgraph Labs, Inc.

2

What token you are talking about?

3

–security token= in dgraph alpha

4

Your situation is quite confusing. You mentioned an issue with whitelisting, which is part of the security config(flag). But you mentioned the “Security Token” which is another option of the security config.

If you have no problem with the Whitelisting, you should not mention it.

If you are really talking about the “X-Dgraph-AuthToken”, you should go to the connection modal, then Extra Settings, and then input the Toke in the input placeholder called “Auth Token”. If I’m not mistaken, it is there where you put the token.

Dgraph doesn’t generate any token, you create it.

Cheers.

PS:

“If set, all Admin requests to Dgraph will need to have this token.
The token can be passed as follows: for HTTP requests, in the
X-Dgraph-AuthToken header. For Grpc, in auth-token key in the context.”