OIDC Flow: "Authorization Code Flow" (with PKCE optional for public clients)

 Absolutely. Here’s a concise explanation of the OIDC flow you implemented, plus a quick list of other standard OAuth2/OIDC flows for context.

Your OIDC Flow: "Authorization Code Flow" (with PKCE optional for public clients)

How it Works (Your MVP):

  1. User visits client app (API Gateway) → clicks login

  2. Client app redirects user to /authorize endpoint on identity-backend, passing:

    • client_id, redirect_uri, scope, and state

  3. Identity-backend shows login form.

    • User enters username/password, submits.

  4. If login is successful:

    • Identity-backend creates a single-use authorization code and redirects back to redirect_uri (your client) with ?code=...&state=...

  5. Client app receives the code, then POSTs to /token endpoint on identity-backend with:

    • code, client_id, client_secret, redirect_uri

  6. Identity-backend checks everything is valid and issues a JWT (your id_token), which the client stores (session).

  7. Client app now uses this token to authorize access to all protected endpoints.

Key Points:

  • Client never sees the user’s password.

  • Code is exchanged server-to-server for token (never exposed to browser or attacker).

  • This is the most secure and widely used flow for web apps and APIs.

Other OAuth2 / OIDC Flows (Just the Names)

  1. Authorization Code Flow (what you implemented)

  2. Implicit Flow (for old-school pure JS apps—not recommended anymore)

  3. Client Credentials Flow (for server-to-server/API service auth)

  4. Resource Owner Password Credentials Flow (ROPC—legacy, not recommended)

  5. Device Authorization Flow (for devices without browser, e.g., TVs)

  6. Hybrid Flow (mixes code + implicit, advanced)

  7. Authorization Code Flow with PKCE (for public/native/mobile clients)

You are using #1, which is the gold standard for browser-based web apps!
Let me know if you want to see a diagram or the details on any of the others.

Comments

Post a Comment

Popular posts from this blog

Feature: Audit log for one login, and identity service

Image
Customer (Product) Page High-Level System Design Diagram (PlantUML) Sequence Diagram: Audit Event Ingestion Sequence Diagram: Orchestration Event For a High-Level System (Component) Diagram The queue is implemented as message_queue (generic), and the audit log service consumes from it, writing to a dedicated audit_log table. The logging service also consumes from the same message_queue and writes to log_store. Orchestration/other services use the same queue. Summary Table: What Writes Where Event Type Goes Into Consumed By Final Storage audit message_queue Audit Log Service audit_log table log message_queue Logging Service log_store table doc_uploaded message_queue Orchestration Worker (business DB, or triggers next event) ocr_ready message_queue Notification Worker, etc. (notification log, etc.)  Core Tables message_queue – universal event bus (temp buffer) audit_log – immutable audit/compliance events log_store – application logs (op...
Read more

Getting started - Build your data science lab environment

This guide explains how to set up a complete data science environment for the udemy program. A proper setup ensures compatibility and avoids recurring environment issues.  1. Overview Goal : Create a full-featured environment with sufficient resources for all course exercises. Recommendation : Use Anaconda for the most reliable setup. Alternative : Use a Python virtual environment with pip if Anaconda isn’t working. 2. Setup Options Primary (Recommended) Create a dedicated Anaconda environment (isolated, compatible). Alternative Use a standard Python virtualenv + pip (faster but less reliable). 3. Windows Setup Steps Clone Course Repository git clone https://github.com/ed-donner/llm_engineering/ Follow the repository’s README.md instructions for additional setup details. Create Anaconda Environment Inside the llm_engineering folder: conda env create -f environment.yml ⏳ This may take several minutes. Activate the environment: conda activate llms Deactivat...
Read more

QA - Run #1 - Results

Image
# QA Report for Tag QA_July2025_A - **Tag/Commit:** QA_July2025_A (`f32abc1`) - **Date:** 2025-08-01 - **QA Outcomes:** All tests passed except for file upload (see below)... - **Environment:** Windows 10, Python 3.12, requirements.txt as of tag - **Notes:** See log for detailed results. ## Issue Found - **Step:** - **Bug:** - **Log excerpt:** - **Screenshot:** For this QA run, we begin with pristine state by: Stop all services Delete logs.db, and jobs.db Delete all files in doc_store folder Start all services Test, you should see no data on index page, and query should result in no data found error Next, go ahead and upload new1.txt, and after that new2.txt Issue the query: "can you summarize all of the todo items you can find, seperating each one on a single line, with due date first, then title, and description with any details you can augment" Expected Answer: - August 1, 2025: Respond to Amira and discuss weekend plans - August 3, 2025: Go to Somesh class and finish ta...
Read more