Common auth issues with Launchpad

Trailing whitespace in the .env file

If you're seeing Bad Request: /auth/userpass, this might be your issue. Make sure STARDOG_INTERNAL_ENDPOINT and STARDOG_EXTERNAL_ENDPOINT don't have any trailing whitespace.

Stardog isn't configured to create tokens

If the following command: 

curl -u user:pass http://stardog-endpoint/admin/token

returns "Stardog is not configured to create tokens", you need to add a signer section to your jwt.conf file. See more here.

Server responds HTTP 204 but with missing CORS headers

The failure appears at the CORS preflight (OPTIONS request) stage when the browser tries to connect to the Stardog endpoint. 

Launchpad v3.8 introduced two new metadata headers (sd-agent and sd-int-ctx) that are sent on requests to Stardog (for Stardog Unit Usage tracking support). These are informational and don't affect authentication, but the browser includes them in the CORS preflight check.

In the v3.7 HAR, the preflight asks permission for just "authorization", and the response comes back with the appropriate Access-Control-Allow-Headers. 

In the v3.8 HAR, the preflight asks for "authorization, sd-agent, sd-int-ctx", and the response comes back with no CORS allow headers at all - so the browser blocks the request before it ever reaches Stardog.

Check that there is not a proxy or load balancer in front of Stardog that may be rejecting these requests because of the presence of these headers.

If there is a reverse proxy or load balancer (e.g. nginx) in front of Stardog that handles CORS, it should have an allowed headers list. Ensure that all three of these are in the header:

•  authorization (existed in v3.7)
• sd-agent (new in v3.8)
• sd-int-ctx (new in v3.8)

If none of these solve your issue

Is there a proxy, load balancer, or firewall running between your machine and Stardog? These commonly cause issues with auth, and you should talk to your network admin about changing your network architecture to allow your machine to communicate with Stardog.

If that still doesn't solve your issue, please file a support ticket and send us your jwt.conf file and .env file.

For more information on auth with Stardog Launchpad, please see our public GitHub repo, onprem-configs.