https://takao.blog/ko/tags/authentication/Recent content in Authentication on Commentary of TakaoHugo -- gohugo.iokoCommentary of TakaoSun, 12 Jul 2026 04:12:51 +0900https://takao.blog/ko/web/webauthn-passkeys/Tue, 02 Apr 2024 00:00:00 +0900https://takao.blog/ko/web/webauthn-passkeys/<img src="https://takao.blog/img/thumbnail/webauthn-passkeys-ko.png" alt="Featured image of post WebAuthn and Passkeys: Passwordless Authentication in 2024" /><p>Passwords have been the primary 인증 mechanism for decades, but they come with well-documented security and usability problems. WebAuthn (Web 인증) and the emerging 패스키 ecosystem promise to replace passwords with cryptographically secure, phishing-resistant 인증. As of 2024, 패스키 support has reached critical mass across all major platforms, making this the ideal time to implement 비밀번호 없는 인증.</p>https://takao.blog/ko/web/oauth-oidc/Mon, 29 Jan 2024 00:00:00 +0900https://takao.blog/ko/web/oauth-oidc/<img src="https://takao.blog/img/thumbnail/oauth-oidc-ko.png" alt="Featured image of post OAuth 2.0 and OpenID Connect: Modern Authentication Guide" /><p>OAuth 2.0 and OpenID Connect form the backbone of modern web 인증 and authorization. Despite their ubiquity, these protocols are frequently misunderstood and misconfigured, leading to preventable security vulnerabilities. This 가이드 covers the core concepts, implementation patterns, and security best practices you need to integrate 인증 securely in your applications.</p> <h2 id="oauth-20-fundamentals">OAuth 2.0 Fundamentals </h2><p>OAuth 2.0 is an authorization framework, not an 인증 protocol. This distinction is critical: OAuth defines how a client application can obtain delegated access to protected resources, but it does not specify how to verify the user&rsquo;s identity. That is where OpenID Connect comes in.</p>