Skip to content

Interface and Operations / Access Token

Added in version 7.5.0

Access Token is an authentication method available for programmatic use. Using an Access Token allows convenient programmatic access to DataFlux Func.

Access Token List

Navigate to 'Manage / Access Token' to access the Access Token list. On this page, you can manage Access Tokens.

access-token-list.png

Configure Access Token

Each Access Token can be configured to enable specific features, and those features can be configured accordingly.

Applications can then authenticate by adding the Authorization header to HTTP requests:

Text Only
1
Authorization: Bearer atk-xxxxx:xxxxx

access-token-setup.png

API Access

When the 'API Access' feature is enabled, HTTP requests carrying this Access Token are allowed to access specified APIs.

This feature supports configuring a rule list. The system will determine whether the current API is allowed to be accessed based on the first matching rule.

You can use * to match any API.

Example: Allow access only to a specific API
1
GET /api/v1/func/overview
Example: Deny access to a specific API, allow all others
1
2
!GET /api/v1/func/overview
*

APIs not matching any rule are denied by default

When an API does not match any rule, it is denied by default.

Therefore, it is unnecessary to add a rule like 'Deny all other APIs' at the end.

MCP Functions

When the 'MCP Access' feature is enabled, MCP clients are allowed to access functions in DataFlux Func by carrying this Access Token.

This feature supports configuring a rule list. The system will determine whether a function in the system is allowed to be called based on the first matching rule.

You can use * to match any function.

Example: Allow access only to functions with category=math
1
category:math
Example: Allow access to functions with category=math and scriptSet ID opencode
1
2
category:math
scriptSet:opencode
Example: Deny access to functions with category=system, allow all others
1
2
!category:system
*

Functions not matching any rule are denied by default

When a function does not match any rule, it is denied by default.

Therefore, it is unnecessary to add a rule like 'Deny all other functions' at the end.

Reference Documentation

For detailed methods on integrating with the DataFlux Func MCP service, please refer to the documentation MCP Service / Accessing Functions