Authentication FAQ

Q. I'm unable to get a new token.

A. There are a couple of reasons you may not be able to get a token.

Your username must be an email address

If you are a long-time GBDX customer, you may have a username that is not an email address. The new authentication system does not accept usernames in any format other than an email address.

  • In the Postman client, check your environment variables. The key "username" should have a "value" that is the email address associated with your account.

  • In gbdxtools, check your config file to make sure the value for user_name is an email address.

You have not signed the latest GBDX Terms of Use agreement

The new authentication system requires users to have sign the latest "GBDX Terms of Use." If you haven't read and signed the latest version, you won't be able get a token.

Q. How do I know if I've signed the latest GBDX Terms of Use agreement?

A. Use your GBDX credentials to sign into

If you need to sign the Terms of Use, a dialog box will appear with the terms and an "accept" button. If you are up to date, the dialog box will not appear.

Q. I'm getting a 401:Unauthorized error when I make an API request.

A. This could be because you haven't signed the latest Terms of Service.

Sign into the web application at If you haven't signed the latest TOS, it will prompt you to read and accept them now. If you still get a 401 error, you can contact for help.

Q. I can't log into the web application

A. Verify that you're using the correct email address and password.

If you're a new user, make sure you've validated your email address. You should have received a welcome email telling you how to do that. If it's been awhile, your invitation may have expired. In that case, contact for assistance.

Q. What version of "gbdxtools" is supported with the new authentication system?

A. We recommend you install 0.14.5 or later.

However, older versions will still work if you clear the token from your gbdxtools config file. See Instructions for gbdxtools Users for more information.

Q. I launched some workflows before the deployment, and they failed and have not restarted.

A. Does the failed workflow use user impersonation?

If your workflows use "user impersonation", they most likely failed due to tokens being expired during the deployment. These workflows will need to be resubmitted.