Glossary

This is an OAuth 2.0 term that refers to user-specific information which is used in place of an ID/password for an application to access a user's resources (information). The authorization server issues a temporary access token to an application, and the application can utilize the user's resources (data) by presenting the access token instead of the user's ID/password.

This refers to an application that requests authorization to the authorization server in OAuth 2.0 and requests a resource owner's data from the resource server. There are a wide range of applications, including services, running on a web server. 

• On this site, this term refers to all services that request authorization to the LG EMP server in order to obtain an access token and request data from the ThinQ platform using the access token.

This is one of the various OAuth 2.0 authorization methods, a method to issue an access token with an authorization code. This method mainly applies to applications running on a web server, and works as follows:

• • If a service (application) requests authorization to the authorization server, the authorization server interacts with the user's web browser (user-agent) to perform authorization.
• • If authorization has been completed, the authorization server issues an authorization code and directs the user's web browser to the predefined Redirect URI. At this time, the authorization code is included in the Redirect URI to be sent to the service.
• • With this authorization code, the service proves to the authorization server that it is "authorized by the user” and receives an access token.
• • https://oauth.net/2/grant-types/authorization-code/

This is an OAuth 2.0 term that refers to a server that confirms an application has been authorized by a resource owner and issues an access token to the application.