This guide describes the methods and corresponding APIs for integrating your application system with IDSEC. By integrating with IDSEC, your application can quickly implement user features such as login, logout, and registration, and incorporate IDSEC's flexible and powerful configuration and management capabilities.
Application Type
Based on common business scenarios, IDSEC categorizes applications into the following types:
Web Application
Application systems that run on backend Web servers are typically developed using languages or frameworks such as Java, .NET, PHP, Node.js, or Express, and users access the applications via browsers. Because backend programs usually run on protected servers, Web applications can securely store sensitive information like application passwords and protect dynamic information such as tokens from being leaked.
Single-Page Application (SPA)
Frontend applications that run directly in browsers are typically developed using technologies such as HTML, CSS, and JavaScript, combined with frameworks like React, Vue, and Angular. Single-page applications can directly send requests to business-plane APIs without requiring backend program forwarding. However, because both the program and data reside in the user-agent (such as a browser), sensitive information that requires protection is not suitable for storage or processing by single-page applications.
Mobile App
Applications that are installed and run on user devices (such as mobile phones, tablets, PCs, and smart devices) are typically developed using dedicated application development languages, such as Objective-C, Swift, or Kotlin. These types of applications are not suitable for storing sensitive information like application passwords, but they can generally protect dynamic information such as tokens from being leaked.
M2M Application (Machine to Machine)
Applications that run on the backend (such as backend services, command-line programs, or daemons) typically implement business features by calling other APIs and do not require user involvement. These applications can effectively protect sensitive information from being leaked.
Access Overview
Web applications, SPAs, and mobile apps can quickly integrate with IDSEC as standard OIDC (OAuth) clients. The OIDC and OAuth protocols are widely used across the internet, and their corresponding development resources are abundant. As a result, applications of various types can generally find development libraries to complete the integration quickly.
M2M applications typically use the Client Credentials Mode to obtain an Access Token and then access the corresponding APIs with that Access Token. Attention:
The APIs described in this guide are accessed via the HTTPS protocol. The access address prefix is your user directory domain name, which you can view on the Domain Settings page. In this guide, https://sample.portal.tencentciam.com is used as the access address prefix.