"Stardog is not configured to create tokens" when using external compute

Created by Steve Place, Modified on Thu, Apr 3 at 10:16 AM by Steve Place

You can get this error even if you enter your Stardog command with username and password. This is because your compute platform (typically Databricks or EMR serverless) is requesting a token from Stardog.


You can test to see if Stardog is configured to create tokens with the following command:

$ curl -u anonymous:anonymous [your endpoint]:[port]/admin/token
{"token": "..."} # expected output
Generic

If you still get "Stardog is not configured to create tokens", you'll need to set up your jwt.yaml file with a signer section, per our documentation.

# This allows Stardog to issue a token for authentication against itself.
signer:
  algorithm: HS256
  audience: my-stardog
  secret: "this-should-be-randomly-generated-secret-key"
  issuer: http://my-domain.com
  tokenTTL: "P30D"
Generic

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article