OLIVE Platform Social Login Implementation Case Study: Resolving Proxy and API Limit Issues

OLIVE Platform implemented Google, GitHub, and Facebook social logins to expand its user base. During this process, it implemented the authentication flow using the Spring Security OAuth2 Client library and adopted a structure that issues JWT tokens to maintain login state.

Key Technical Implementation and Unlinking

On the server side, the spring-boot-starter-oauth2-client dependency was added, and Client Registration and Provider settings were customized. In particular, the social login unlinking feature was not provided by default in the library, so it was implemented by directly calling the permission revocation APIs of each platform.

Issues Encountered During Actual Service Deployment and Solutions

While working normally in the development environment, the following issues occurred in sandbox and production environments.

• Profile Photo Loading Failure: Facebook's profile photo API redirects, which caused it to be blocked by proxy policies. This was resolved by extracting the actual image URL using the redirect=false parameter and adding the corresponding domain to the proxy allowlist.
• API Request Limits (Rate Limit): Facebook has an API request limit of 'total number of users x 200' per hour. The logic was optimized to reduce unnecessary API calls and only invoke them during login and sign-up.
• App Review and Production Mode Transition: Google app review was required due to adding a logo, etc. The transition to production mode was completed after entering OAuth consent screen information and verifying domain ownership (registering a TXT record in Google Search Console).

Ultimately, OLIVE Platform stably services a total of four social login features, including Kakao.