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
  • Create Group
  • Search Group
  • View Group
  • Update Group
  • Delete Group

Was this helpful?

Export as PDF
  1. Guide
  2. Client Management

API Group

PreviousAPI ClientNextAPI Scope

Was this helpful?

Path: Client Management > API Group

API Group is for creating and maintaining API groups. APIs with the same authentication type can be placed in the same group here; APIs in this group will correspond to authorizable client permissions according to the security levels originally set; when selecting the API Scope, a group is used as the unit and authorized at once. This function is usually used to authorize API clients.

Take the figure below for example. The Module list has three groups /A, /B and C, in which group C contains the four APIs #C1, #C2, #C3 and #C4. If users need to use them, all four APIs in the group will be authorized for them at once.

Create Group

  1. Click Create Group to access the group creation page.

  1. Fill in the data or make selections as instructed below. The fields marked with “*” are required.

  • Group name*: Cannot be changed.

  • Group alias: Alias to help identify the group.

  • Allowed access duration*: Number of days valid for this group; it will become invalid once expired.

If set to 0, it means there are no limits.

  • Number of allowed access times*: The maximum number of times this group of APIs can be authorized; it can no longer be used after the number of times has exceeded.

If set to 0, it means there are no limits.

  • Authentication type: Authentication type is required for the APIs in this group; multiple choices allowed.

  • Security level*: Security levels include A~F; the security level must correspond to the security level of the client’s account.

    • Simply select the default system security for the security level.

  • Description:Description or remarks of the group.

  • API Module: Enter to select the API module currently mounted on the digiRunner platform.

  1. Further instructions for completing the fields.

  • API Module: Click Select to enter and select the API module currently mounted on the digiRunner platform.

    • Access the selection page and search for the module to add with the search field, then click Select to the left to add it into the module list. To cancel, click Delete to the right side of the selected module; make sure to click Apply when finished selecting.

  • At this time, module is added but not API. It is only added to the group name, but there is nothing inside. Click Select API to complete adding API to the module.

  • After selecting the API to add, click Apply.

  • If the group is created with no API added to the module, this module will not be added to the group. Take the figure below for example. APIs are added to /UserManual, and no API is added to /UserManualDgrcGet2. Upon clicking Create, only /UserManual will be saved to the group and not /UserManualDgrcGet2.

  1. Click Create to save and exit.

Search Group

To search for a group, enter the keywords or the authentication type or security level here to search for related groups.

View Group

The information in Details can only be viewed and not edited.

Update Group

To add modules and APIs, the method is the same as to create a group.

  1. Modify the desired fields, and click Update to save and exit.

Delete Group

  1. Click Delete to delete the group and exit.

Delete the group in the Delete group page, the warning prompt for deletion will NOT appear.

If this group is set as available to a client in API Client > Security > API Group, the error “1417 - Group has been used by Client” will appear, meaning that this group is in use and cannot be deleted.

If C is selected as the security level for the client, security levels A and B cannot be found here at API Group. For more information, refer to .

Authentication type:Click on the icon to access and select from the authentication list; multiple choices allowed as mentioned above.

Search for the group to view details, and click on theicon to access the group details page.

Search for the group to modify, and click theicon to access the update page.

Search for the group to delete, and click on the icon to proceed.

Security level