SSO and OAUTH Note

OAUTH was mentioned a lot in previous posts.
SSO stands for Single Sign On, which is how to automatically access and use different sites with one login from multiple sites. Typically, different systems, different sites, manage each user's information. However, it may be necessary to use each user's information in conjunction with the need. Therefore, each information is left intact and the integration certificate is used. When logging in to each system, check that there is integrated authentication information, and if there is an integrated authentication information, the other system automatically logs in and the integrated authentication information is generated to be referenced by other systems.
Single Sign On (SSO) addresses these issues. Users only need to remember their account, and log in once when using multiple systems. Administrators can also manage membership information in one place, reducing management points.

There are many ways to configure SSO, but it can be summarized in two ways. The first is to use the CAS server, an open source dedicated to SSO, and the other is to configure SSO using OAuth 2, which provides access control flow to service resources. OAuth 2 enables excellent expansion into web, mobile, desktop, and IoT devices.