LogoLogo
TPI.devCommunityGithub
  • Overview
    • Introduction
      • Future Features
    • License & Disclaimer
    • APIM Architecture
      • Production Deployments and Capacity
      • Functions
      • Integration
    • Key Concepts
      • API Group
      • API Scope
      • API Client
      • End-to-End Workflow Combining API Group, API Scope, and API Client
        • Scenario: API Management for an E-commerce Platform
    • Support
    • Glossary
    • Scenarios
      • Financial Industry
        • Transforming Financial Services with digiRunner API Management
        • Redefining Financial Data Migration with digiRunner API Management Platform
      • Manufacturing Industry
        • Enabling Smart Manufacturing with Seamless API Integration and Automation via digiRunner
        • Streamlining Global Operations with API Management via digiRunner
      • Medical Industry
        • Enhancing Healthcare Data Integration and Security with digiRunner API Management
        • Revolutionizing Healthcare Interoperability with digiRunner’s Advanced API Framework
      • Insurance Industry
        • Modernizing Insurance Services with digiRunner API Management
        • Modernizing Insurance with digiRunner—Bridging Legacy Systems and Microservices
      • Government and Public Services
        • Empowering Open Government Services with digiRunner: A Mission for Integration and Transformation
        • Streamlining Public Sector Innovation via digiRunner: Driving Citizen-Centric Digital Transformation
  • Get Started
    • Installing digiRunner API Management
      • SMTP Configuration
    • Registering Your First APIs with digiRunner
    • Client Authorization and Calling APIs
    • Rate Limiting
    • Proxy Caching
    • Load Balancing
    • Sandbox Testing
    • VIP Gateway Priority Settings
    • JWE Certificate
  • Configuring IP Whitelisting via IP Binding
  • Most common use cases
    • Obtaining API Keys and Calling APIs
    • API IP Diversion
    • Viewing Real-time API Logs
    • Enabling APIs and No Auth in Batches with API Imported
    • Role-Based Access Management within a Hierarchical Structure
    • Simplified OIDC Login with Predefined Organizational Frameworks
    • Resetting User Password and Confirmation Email for Admin Console User
  • Guide
    • AC User Management
      • Users
      • My Profile
      • Roles
      • Role Mapping
      • Organization
      • Role & txID
      • Delegate AC User
      • AC OAuth 2.0 IdP
      • AC LDAP IdP
      • AC MLDAP IdP
      • AC API IdP
    • Development Mode
      • Function Management
      • Rtn Code Management
      • Embedded Function Management
    • Client Management
      • API Client
      • API Group
      • API Scope
      • Authentications
      • Security Level
      • GTW OAuth 2.0 IdP
      • GTW LDAP IdP
      • GTW API IdP
      • GTW JDBC IdP
      • Client Export/Import
    • API Management
      • API List
      • API Registry
      • API Test
      • API Modify Batch
    • Monitor & Alert
      • digiRunner Server
      • Alert Settings
    • Reports
      • API Calls
      • API RESP distribution
      • API Avg. RESP Time
      • API GTW traffic
      • Bad Attempt Report
    • Certificate Management
      • JWE Cert. List
      • JWE Cert. Management
      • TLS Cert. List
      • TLS Cert. Management
    • Application Forms
      • API Key
      • Applications
      • Approval Flow Settings
    • System Information
      • API Key Approval History
      • Scheduled Tasks
      • Recurring Tasks
      • Mail Log
    • System Configs
      • Setting
      • Items
      • Files
      • Customer Setting
      • Online Console
      • WebSocket Proxy Management
      • Static Webpage Reverse Proxy
      • RDB Connection
      • Mail Template Export/Import
  • API Integration Guide
    • Using Token for Authentication and Authorization
      • OpenID Connect (OIDC) Mode
      • Client Credentials Mode
      • Password Mode
    • Using X API Key for Authentication and Authorization
      • Applying for X API Key
      • Obtaining X API Key
      • Calling APIs Registered in digiRunner with X API Key
    • Using API Key for Authentication and Authorization
      • Applying for API Key
      • Obtaining API Key and Secret Key
      • Calculating the Signature and DGRK
      • Calling APIs Registered in digiRunner with API Key
    • Using HTTP Basic and OAuth for Authentication and Authorization
      • Calling APIs Registered in digiRunner with Basic Auth
      • Calling APIs Registered in digiRunner with No OAuth
    • Token Lifecycle Management Mechanism
      • Applying Refresh Token
      • Token Revocation
      • Token Introspection
    • JWS/JWE Integration
      • JWS Workflow
      • JWE Workflow
      • Exchanging Public Keys
      • Generating Certificate
      • Operating with JWS
      • Operating with JWE
Powered by GitBook
On this page
  • Export Clients
  • Import Clients

Was this helpful?

Export as PDF
  1. Guide
  2. Client Management

Client Export/Import

PreviousGTW JDBC IdPNextAPI Management

Was this helpful?

Path: Client Management > Client Export/Import

In this section, you can find instructions on how to import and export the client data.

Export Clients

To export the client date, click Export to export the .json file of the desired client.

Import Clients

In this section, you can find instructions on how to import the client data, along with important notes.

Import Process

  1. To import client-related data, click Import, select the desired JSON file, and click Upload.

Do not modify the content of the JSON file; altering the original data may cause system errors.

  1. Click Upload to automatically compare the new data with the existing data. If the data is new, the Data status will display as Add; if the data is unchanged, the Data status will display as Repeat.

  1. If Lack API appears, it indicates that some APIs on the system have been deleted or modified. You can either check the option "It has been confirmed that if the API used by the client is missing, it will be ignored. If it is not checked, the import operation will not be processed. Please re-import after correction", or manually add the missing APIs to the system.

  1. Click Covered all to display the addition or overwrite status of each setting, allowing the user to confirm the changes.

  1. A warning prompt displaying the message “Confirm cover all” will pop up. Click Confirm to overwrite all.

  1. The Data status will change from red to black.

  1. Click Confirm to successfully import the client data.

Important Notes

The criteria for identifying duplicate data are listed below:

  1. Client Info: Based on the client account.

  • The API status used by DP, such as application authorization API and login authorization API, will be transferred.

  • Cannot add or overwrite in the following cases:

    • If the code or name is duplicated, it cannot be added or overwritten.

    • If the host list's name or IP is duplicated with other data, it cannot be overwritten.

    • If the security levels are different, it cannot be overwritten.

  • Will not be overwritten in the following cases: Passwords and the number of password errors will not be overwritten.

  1. Group: Based on the group code.

  • Cannot overwrite in the following cases:

    • The name is duplicated with an existing group.

    • The state cannot be added.

  1. Authorization Scope: Based on the API scope code.

  • Cannot overwrite in the following cases:

    • The name is duplicated with an existing API scope.

    • There are more than 186 APIs.

    • The state cannot be added.

  1. Authentications: Based on the authentication method code.

  • Cannot overwrite in the following cases:

    • The name is duplicated with an existing authentication name.

    • The state cannot be added.

  1. Security Level: Based on the security level code.

  • Cannot overwrite in the following cases:

    • The name is duplicated with an existing security level.

    • The state cannot be added.

  1. RDB Connection: Based on the connection name.

  • The HikariConfig Data Source Properties will use new values for overwriting.

  1. If the data status displays in red, it indicates that the data is not processed.