What is the endpoint of a namespace on a dedicated server?

[Poolshark (Flo Ragossnig)]

Thanks for the quick reply!

@MichelDiz

You can hide any key behind via NGINX header passthrough proxy_set_header X-Dgraph-AccessToken your-key-here. But never do this with admin keys. Cuz with admin you can edit/see /admin configs.

Well, I would still need to bundle the admin key with my app, right? I have to use the admin key because the login mutation only exists on the /admin endpoint. That’s what confused me so much. How is this supposed to work and why is the Tenant-0 always exposed to public?

Here’s what I did to get the accessJWT when I query against the graphql endpoint:

type Tokens {
  accessJWT: String
  refreshJWT: String
}

type LoginPayload {
  response: Tokens
}

type Mutation {
		getTokenForNamespace(userId: String, password: String, namespace: Int, refreshToken: String): LoginPayload @custom(http: {
			url: "https://<endpoint>/admin",
			method: POST,
			secretHeaders: [
        "DG-Auth:AdminKeyTesting"
      ],
    	introspectionHeaders:["DG-Auth:AdminKeyTesting"]
      graphql: "mutation($userId: String, $password: String, $namespace: Int, $refreshToken: String) { login(userId: $userId, password: $password, namespace: $namespace, refreshToken: $refreshToken) }"
		})
}



# Dgraph.Secret AdminKeyTesting "YOUR-ADMIN-KEY-HERE"

@MichelDiz

Not sure, there is a new guideline from Google that prohibits browsers and engines from communicating with non-HTTPS applications whether it comes from a protected site or not. Only HTTP to HTTP or HTTPS to HTTPS.

Why does it work on the Shared Cluster then?