GoodData Token Types
Many actions in the GoodData platform require (or result in) a generated token.
Typically, a GoodData token is a hashed value that provides a unique reference within Your GoodData Domain to:
- An object, for example, a workspace
- An action, for example, a SQL query that performs a specific change in the platform.
This article provides basic information on the different types of GoodData tokens.
When you perform technical references to a workspace in the GoodData platform, you typically refer to the workspace using the authorization token.
Depending on your GoodData license, you should have been provided a workspace authorization token, which enables you to create a predefined number of workspaces in the platform.
In GoodData, terms workspace and project denote the same entity. For example, project ID is exactly the same as workspace ID.
If you are creating new workspaces in the GoodData platform, you must submit to the workspace creation API a workspace authorization token. This token enables the user of it to create a new, empty workspace in the platform.
When you use the GoodData APIs to perform full or partial exports of a workspace, the platform returns a token, which you can use to reference the bundled content. The export API generates a token in the response, which must be retained. When the import API call is made, the token must be included in the request. For more information on full or partial workspace exports and imports, see the API documentation on exporting and importing workspaces.
Logging to the GoodData platform requires two tokens.
Use of these tokens is necessary if you are accessing the platform from a non-browser interface, such as the GoodData APIs.
- super-secure token (SST) - When you first login to the GoodData platform, you receive in the response header the SST. This token must be included whenever you query for a temporary token.
- temporary token (TT) - Using the token API, you can generate a temporary token, which is valid for 10 minutes. Any request for workspace objects requires the use of a temporary token as part of the request. When it expires, you must renew it.
For more information, see Authentication via API.
And Other Tokens…
Since GoodData supports integration with a wide variety of enterprise platforms, you may be required to manage tokens issued from those platforms for authentication and object reference.