OAuth2 & OpenID Connect Deep Dive · レッスン

OIDCを使用したImplicit Flow

OIDCのImplicit Flowについて学び、ID Tokenを直接返す仕組みと、シングルページアプリケーションにおけるセキュリティ上の影響を理解します。

「OIDCを使用したImplicit Flow」はCoddyKit上の無料OAuth2 & OpenID Connect Deep Diveレッスンです。これはレッスン2/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはOAuth2 & OpenID Connect Deep Dive学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 OAuth2 & OpenID Connect Deep Diveコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

OIDC Implicit Flow Basics

What is the Implicit Flow with OpenID Connect (OIDC)? It's a way for web applications, especially Single-Page Applications (SPAs), to get identity information and access tokens directly from the authorization server.

It was designed for scenarios where a backend server couldn't securely store a client secret.

Direct Token Delivery

Unlike the Authorization Code Flow, the Implicit Flow doesn't involve an authorization code exchange with the authorization server's token endpoint.

Instead, the ID Token and Access Token are returned directly to the client's browser in the URL fragment after user authentication.

Requesting Tokens Directly

The client application initiates the flow by redirecting the user's browser to the Authorization Server's /authorize endpoint.

Key parameters include:

response_type=id_token token: Requests both an ID Token and an Access Token.
client_id: Identifies the client application.
redirect_uri: Where the user is sent back after authentication.
scope=openid profile: Specifies requested permissions, including openid for OIDC.
nonce: A unique string to prevent replay attacks.

https://auth.example.com/authorize?
  response_type=id_token%20token&
  client_id=my-spa-client&
  redirect_uri=https://app.example.com/callback&
  scope=openid%20profile&
  nonce=aRandomNonceValue&
  state=aRandomStateValue

Tokens in the URL Fragment

After the user successfully authenticates and grants consent, the Authorization Server redirects the user's browser back to the redirect_uri.

The tokens (ID Token and Access Token) are included directly in the URL's fragment part (after the # symbol).

The client-side JavaScript then reads and processes these tokens.

https://app.example.com/callback#
  id_token=eyJ...&
  access_token=eyJ...&
  token_type=Bearer&
  expires_in=3600&
  state=aRandomStateValue

Client-Side Token Processing

Since the tokens are in the URL fragment, they are accessible to client-side JavaScript. The browser does not send the fragment to the server.

The SPA extracts the id_token and access_token, validates them, and can then use the access_token to make requests to protected API resources.

public class TokenParser {
  public static void main(String[] args) {
    String urlFragment = "id_token=eyJ...&access_token=eyJ...&expires_in=3600";
    System.out.println("Processing URL fragment:");
    String[] params = urlFragment.split("&");
    for (String param : params) {
      String[] pair = param.split("=");
      if (pair.length == 2) {
        System.out.println(pair[0] + ": " + pair[1]);
      }
    }
    System.out.println("\nIn a real app, you'd validate these tokens!");
  }
}

Identity with the ID Token

The ID Token is a JSON Web Token (JWT) that contains claims about the authenticated user, such as their unique identifier, name, and email.

The client application validates this token to verify the user's identity and ensures it came from the expected Authorization Server.

This is the "identity layer" OpenID Connect adds to OAuth2.

Security Risk: Browser History

A major security concern with the Implicit Flow is that tokens are exposed in the browser's URL fragment.

This means they can be stored in browser history, server access logs (if the fragment is accidentally included), and potentially accessed by other scripts on the same page.

Browser History: Tokens might be saved, allowing unauthorized access if someone gains access to the browser history.
Referrer Headers: In some cases, tokens could leak via Referrer headers.

Security Risk: No Client Secret

The Implicit Flow is typically used by "public clients" (like SPAs) that cannot securely store a client secret.

This means the Authorization Server cannot authenticate the client application itself, only the user. This makes it vulnerable to certain attacks, such as token injection.

An attacker could potentially inject a malicious token.
There's no cryptographic proof that the client receiving the token is the one that initiated the request.

Discouraged & Replaced

Due to its inherent security weaknesses, the Implicit Flow is now largely deprecated for new implementations.

The OAuth 2.0 Security Best Current Practice recommends using the Authorization Code Flow with PKCE (Proof Key for Code Exchange) for public clients like SPAs and mobile apps.

PKCE provides a robust way to secure public clients without requiring a client secret.

Implicit Flow Quick Check

Which of the following is a primary security concern when using the OIDC Implicit Flow?

Implicit Flow Recap

We've explored the OIDC Implicit Flow, where identity and access tokens are returned directly in the URL fragment.

While it simplifies client-side access, its security risks, primarily token exposure in the URL and lack of client authentication, have led to its deprecation.

Always prefer the Authorization Code Flow with PKCE for public clients to ensure robust security.

よくある質問

「OIDCを使用したImplicit Flow」レッスンは無料ですか？

はい。「OIDCを使用したImplicit Flow」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、OAuth2 & OpenID Connect Deep Diveコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 OAuth2 & OpenID Connect Deep Diveコースには全4レッスンが含まれています。

「OIDCを使用したImplicit Flow」で何を学びますか？

OIDCのImplicit Flowについて学び、ID Tokenを直接返す仕組みと、シングルページアプリケーションにおけるセキュリティ上の影響を理解します。ブラウザで直接実行するハンズオンコードでOAuth2 & OpenID Connect Deep Diveを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

OAuth2 & OpenID Connect Deep Diveを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのOAuth2 & OpenID Connect Deep Diveは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン2/4です。

「OIDCを使用したImplicit Flow」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このOAuth2 & OpenID Connect Deep Diveレッスンでコードを書いて実行できますか？

はい。すべてのOAuth2 & OpenID Connect Deep Diveレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← OAuth2 & OpenID Connect Deep Diveに戻る