Skip to main content
Version: 8.3.0

Token Management

Overview

Token Management configures credentials used by external systems to call Guandata BI Public APIs. Administrators can manage the legacy default token or create separate Public API applications with individual authentication, permission scopes, and security settings.

FeatureScenario
Default TokenCompatibility for legacy integrations that call Public APIs through public-token.
Public API Application ManagementCreates an independent application for each new integration.
Note

The default token exists only for compatibility with the legacy public-token channel. Use Public API applications for new integrations, and disable the legacy channel after existing callers migrate.

Open Token Management

Go to Management Center > Open Platform > Token Management to configure the default token and its IP allowlist and manage Public API applications.

Manage the default token

Enable or disable the legacy channel

The Allow other systems or modules to access related information switch controls the legacy public-token channel. When disabled, the default token can no longer call related Public APIs through that channel.

Copy or regenerate the default token

In Default Token, copy the current token or click the refresh button to generate a new one.

Risk

The default token is an external-system credential. Never include it in public documentation, repositories, tickets, or chat messages. Regenerating it immediately breaks callers using the old value; update every dependent system.

Configure the IP allowlist

In IP Whitelist (highly recommended), enter permitted IP addresses and separate multiple values with commas. Restrict the token to actual caller addresses whenever possible.

Create a Public API application

  1. In Public API Application Management, click Create Application.
  2. Enter the Application Name and Description.
  3. On Authentication mode, confirm the authentication method. OAuth2 is currently supported.
  4. On Permission Scope, select the access required by the integration.
  5. Complete the application security configuration under Security Settings.
  6. Click Save.

The list shows application name, App ID, authentication method, permission scope, and status. Use the Action column to continue managing an application.

Difference from OIDC Management

Token Management creates and manages applications that call Public APIs. OIDC applications are created by an administrator in OIDC Application Management in the administration console. OIDC Management in Management Center only controls current-domain access for existing OIDC applications and limits Access Token and Refresh Token lifetimes.

Public API applications and OIDC applications are different types. A Public API application cannot serve as an OIDC login credential and does not appear in the Application (RP) list under OIDC Management.