If you suspect this could be a bug, follow the template.
What version of Dgraph are you using?
v1.0.15
Have you tried reproducing the issue with latest release?
Yes
What is the hardware spec (RAM, OS)?
Mac, 16gb ram
Steps to reproduce the issue (command/config used to run Dgraph).
Using the live loader to import, there is no way to specify auth for loading in RDF’s/JSON data, even though there is for altering the schema.
Expected behaviour and actual result.
The auth token should be used for mutations as well as schema alters but right now it’s only being used for schema alters and all mutations are denied based on ACL permissions.
Hi @nodeworks , thanks for letting us know your experience.
The auth token is intended for open source users who don’t have access to the ACL feature, which is an enterprise feature. If you do have a contract with us and are using ACL, you don’t need to use the auth token anymore as the mechanisms in ACL is more secure than the auth token.
In the live loader, I’ve just added the support of user login through the --user and --password options. Please try it out and let us know if you still have issues.