Token Cache
Overview
Below is a business-focused explanation of the Token Cache document type, written for functional users and business stakeholders.
Token Cache – Business Overview
What the Token Cache is used for
The Token Cache is a system-level record used by Dafater to securely remember access permissions when it connects with external services.
In simple terms, it allows Dafater to “stay logged in” to approved third‑party platforms so that business processes can run smoothly without repeated manual approvals.
This ensures that integrations such as banking services, payment providers, identity services, or external data sources continue working without interruption.
Prerequisites and setup requirements
Before the Token Cache is used, the following must already be in place:
- A business-approved integration with an external service
- Valid access credentials provided by that external service
- Management approval for automated data exchange
- Defined rules on how long access should remain active
Once these prerequisites are met, Dafater automatically manages the Token Cache in the background.
Typical workflow and business process fit
The Token Cache fits into business operations as a silent enabler:
- A business process requires data or action from an external service
- Dafater checks the Token Cache to confirm valid access
- If access is still valid, the process continues without interruption
- If access has expired, Dafater refreshes or replaces the token automatically
- Business users experience uninterrupted operations
Users do not manually create or update Token Cache records during normal operations.
Key business scenarios where Token Cache is essential
The Token Cache is critical in scenarios such as:
- Automated payment processing and transaction verification
- Continuous data exchange with financial institutions or partners
- Identity or verification checks during onboarding processes
- Scheduled data synchronization with external platforms
- Any process where repeated secure access is required without user involvement
Without the Token Cache, these activities would require frequent manual re‑authentication, slowing down operations.
Important considerations for users
- The Token Cache is managed automatically by Dafater and usually does not require user action
- Business users should not modify or delete records unless instructed by system administrators
- Unexpected integration failures may indicate an expired or invalid token
- Regular review of active integrations helps ensure compliance and security
- Access rules should align with internal governance and audit policies
Business value summary
The Token Cache ensures reliability, security, and efficiency in integrated business processes. By safely storing access permissions, it allows Dafater to support continuous operations, reduce manual effort, and maintain trusted connections with external services.
Basic Information
- Module: Integrations
- Document Type: System
Fields
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| user | User | Link | User | Dafater user associated with the stored authentication token | |
| connected_app | Connected App | Link | Connected App | External application connected to Dafater using this token | |
| provider_name | Provider Name | Data | - | Authentication provider name issuing the token | |
| access_token | Access Token | Password | - | Encrypted access token for authorized API requests | |
| refresh_token | Refresh Token | Password | - | Encrypted token used to refresh expired access tokens | |
| expires_in | Expires In | Int | - | Token validity duration in seconds | |
| state | State | Data | - | OAuth state value for request validation | |
| scopes | Scopes | Table | OAuth Scope | List of permissions granted to the connected application | |
| success_uri | Success URI | Data | - | Redirect URI after successful authentication | |
| token_type | Token Type | Data | - | Type of authentication token issued |
Child Tables
Scopes (OAuth Scope)
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| scope | Scope | Data | - | Defines API access permissions granted to applications |
Permissions
| Role | Read | Write | Create | Delete | Submit | Cancel |
|---|---|---|---|---|---|---|
| All | ✓ | ✓ | ||||
| System Manager | ✓ | ✓ |
Related DocTypes
| DocType | Relationship | Module |
|---|---|---|
| Connected App | Links to | Integrations |
| User | Links to | Core |