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
  • Creating API Groups
  • Creating Client Accounts and Authorizing Groups
  • Verifying Registered APIs with Client Credentials

Was this helpful?

Export as PDF
  1. Get Started

Client Authorization and Calling APIs

PreviousRegistering Your First APIs with digiRunnerNextRate Limiting

Was this helpful?

When internal/external personnel need to use APIs, a set of account and password needs to be acquired first, then pass client management authorization before they can be used. Users can also add and edit the API groups they need to use in groups, and when users and groups have matching security levels, clients can call the APIs in the group.

Group - A list of all APIs that control authorization; APIs authorized to be called successfully through Auth are defined by groups.

Client - To perform account and password verification for Auth authorization through the client, permission to call group APIs need to be obtained from the action of authorization groups.

Creating API Groups

The scope of authorization can refer to the establishment operation of group maintenance.

  1. Go to Client Management > API Group, and click Create Group.

  1. Fill in the required fields.

  1. If there are APIs that require authorization, you need to go to the Module list field and click Select.

  2. Go to the Module list and select the Module to authorize, and click Select.

  3. It will move to the list of selected Modules, then click Apply.

  1. Next, click Select API for that Module, and go to the list to select the API to authorize, then click Select.

  2. It will move to the list of selected Modules, then click Apply. Return to the New page and click Create.

  1. Creation of the group is completed, go to the API Group page and the data entry can be queried.

If you need more help when creating a API Group, please refer to the following link for more information.

Creating Client Accounts and Authorizing Groups

Creating Client Accounts

  1. Go to Client Management > API Client, and click Create.

  1. Fill in the required fields.

  2. Click Active for the Status field, and select Internally for the API Audience field.

  3. Although the E-mails field is not required, but it is still recommended to fill it in since there is the E-mail verification function.

  4. Click Create to complete the creation.

  1. Go to the API Client page to verify if the entry has been successfully created.

If you need more help when creating a API Client, please refer to the following link for more information.

Authorizing API Groups for Client Use

  1. Click the API Group tab to enter the authorization setting page, then click Add.

  1. Search for the created group, then click Update after selecting the group.

  1. Confirm that the authorization setting page has data of connected groups displayed on the list to finish connection.

Verifying Registered APIs with Client Credentials

APIs registered in the system can use different OAuth Grant Type for verification.

Note: For other authorization methods such as Password and Basic Auth, etc., please refer to their corresponding processes.

  1. Go to API Management > API Test, and the digiRunner URL field will automatically populate with the API URL registered in digiRunner.

  2. In the Authorization field, select Client Credentials.

  3. In the Client ID and Client password fields, fill in the client account and password that are registered and authorized for the API.

  4. Click Test to view the response. In this example, the status code is 200, indicating the body contains the data defined by the API.

Go to Client Management > API Client, select a client and click on the Security icon .

API Group
API Client