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
  • Example of Successful Response
  • Example of Error Response

Was this helpful?

Export as PDF
  1. API Integration Guide
  2. Token Lifecycle Management Mechanism

Token Introspection

Verify the legitimacy of the access token or refresh token.

Example request:

curl -v -X POST https://{digiRunner_DOMAIN}/oauth/introspection \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'token={access_token}' \
-d 'token_type_hint=access_token' \
-d 'client_id={client_id}' \
-d 'client_secret={client_secret}'

Parameters with details:

Parameter
Type
Requirement
Description

token

String

Required

Token to be introspected

token_type_hint

String

Required

Specifies which type of token to introspect:

To introspect an access token, use access_token as the value; to introspect a refresh token, use refresh_token as the value

client_id

String

Required

Client ID registered with digiRunner

client_secret

String

Optional

Scenario I. Higher-Security (Client Password Required)

Client Password registered with digiRunner

Scenario II. PKCE + Public Client (Client Password Not Required)

When the Public Client (With PKCE) option is selected in digiRunner's OAuth grant type, the parameter is not required.

Example of Successful Response

Example:

{
"active": true,
"scope": "openid email profile 2000000086 2000000088",
"client_id": "tspldapclient",
"username": "Tsp Lee",
"token_type": "access_token",
"exp": 1685513177,
"iat": 1685426777,
"nbf": 1685426777,
"sub": "tspldapuser",
"aud": "YWRtaW5BUEk",
"iss": "https://10.20.30.88:18442/dgrv4/ssotoken/LDAP",
"jti": "882207db-4f84-433c-9508-1e1fb077ae13"
}

Parameters with details:

Parameter
Type
Description

active

Boolean

Indicates whether the token was issued by digiRunner, hasn't been revoked by the resource owner, and is still within its valid period. Returns true or false.

scope

String

Specifies the range of resources that the access token is granted permission to access

client_id

String

Use client_id as the value for OAuth

username

String

Identifies the user who authorized this token, such as an alias on the application

token_type

String

Indicates the type of the token, such as access_token or refresh_token

exp

Number

Token expiration time, an integer indicating the seconds since 1970-01-01T00:00:00Z UTC

iat

Number

Token issuance time by the OAuth Server, an integer indicating the seconds since 1970-01-01T00:00:00Z UTC when the token is issued by the OAuth Server.

nbf

Number

Token invalid time, an integer indicating the seconds since 1970-01-01T00:00:00Z UTC before the token becomes valid

sub

String

Identifies the user who authorized the token

aud

String

Indicates the audience intended to use the token

iss

String

Indicates the authorization server issuing the token

jti

String

Unique ID of this token, such as a UUID used when storing the token in a database to prevent replay attacks

Example of Error Response

If the client password is incorrect, a 401 Unauthorized HTTP status code and JSON response will be returned.

Example:

{
"timestamp": "1685332598344",
"status": 401,
"error": "Unauthorized",
"message": "The client account or password is incorrect. clientId: tspldapclient",
"path": "/oauth/introspection"
}
PreviousToken RevocationNextJWS/JWE Integration

Was this helpful?