
Sukmo worked on the Kernel360/blog repository, delivering two technical blog posts that addressed authentication and integration challenges in Java-based systems. He documented the implementation of Google OAuth2 and JWT login in Spring Boot, analyzing security aspects such as CSRF with SameSite=None and proposing enhancements like refresh tokens and token blacklisting. In another post, he clarified the differences between HTTP/1.1 and HTTP/2 in the context of Firebase Cloud Messaging, diagnosing a protocol incompatibility and providing a practical workaround. His work combined technical writing, security analysis, and hands-on Java development, offering clear guidance and reusable documentation for future engineering efforts.

April 2025 monthly summary for Kernel360/blog: Delivered a technical guidance post clarifying HTTP/1.1 vs HTTP/2 in the context of a Firebase Admin Java SDK/FCM integration issue. Diagnosed that 'Host: fcm.googleapis.com' is not compatible with HTTP/2 messaging and documented a reliable workaround by forcing HTTP/1.1 to avoid the error in production scenarios. The work aids developers, reduces debugging time, and informs future architecture decisions. Committed as 0b6dfa294dab6a3ae6d5306efc991a07db1b7b30.
April 2025 monthly summary for Kernel360/blog: Delivered a technical guidance post clarifying HTTP/1.1 vs HTTP/2 in the context of a Firebase Admin Java SDK/FCM integration issue. Diagnosed that 'Host: fcm.googleapis.com' is not compatible with HTTP/2 messaging and documented a reliable workaround by forcing HTTP/1.1 to avoid the error in production scenarios. The work aids developers, reduces debugging time, and informs future architecture decisions. Committed as 0b6dfa294dab6a3ae6d5306efc991a07db1b7b30.
February 2025: Kernel360/blog focused on documenting and presenting Google OAuth2 + JWT login integration in Spring Boot. Key deliverable: a technical blog post detailing implementation, security implications (CSRF with SameSite=None), and proposed enhancements such as Refresh Tokens and a blacklist. This work provides a clear reference for secure authentication, supports future implementation, and demonstrates disciplined documentation alongside code changes. No major bug fixes recorded for this period. Technologies demonstrated include Spring Boot, Google OAuth2, JWT, CSRF mitigation, and documentation-driven development.
February 2025: Kernel360/blog focused on documenting and presenting Google OAuth2 + JWT login integration in Spring Boot. Key deliverable: a technical blog post detailing implementation, security implications (CSRF with SameSite=None), and proposed enhancements such as Refresh Tokens and a blacklist. This work provides a clear reference for secure authentication, supports future implementation, and demonstrates disciplined documentation alongside code changes. No major bug fixes recorded for this period. Technologies demonstrated include Spring Boot, Google OAuth2, JWT, CSRF mitigation, and documentation-driven development.
Overview of all repositories you've contributed to across your timeline