Visualize API Request Flow Documentation

Problem/Feature Description

A development team is onboarding new engineers and needs clear documentation of how their authentication system works. The current written documentation describes a multi-step OAuth flow where a client requests access, the server validates credentials, generates tokens, and returns them through several stages. New developers are struggling to understand the sequence and timing of these operations.

Your task is to create educational documentation that explains this authentication flow. The documentation should help new engineers understand both the sequence of operations and the relationships between components.

Input Files

The following files are provided as inputs. Extract them before beginning.

=============== FILE: inputs/auth-flow-description.txt ===============

OAuth2 Authentication Flow

Our system implements a standard OAuth2 authorization code flow with PKCE (Proof Key for Code Exchange).

Step-by-Step Process

1. Client generates a code verifier and code challenge
2. Client redirects user to authorization endpoint with code challenge
3. User authenticates and grants permissions
4. Authorization server redirects back with authorization code
5. Client exchanges authorization code + code verifier for access token
6. Authorization server validates the code and verifier match
7. Server issues access token and refresh token
8. Client stores tokens securely

Component Relationships

The system involves these main components:

• Client Application (web or mobile app)
• Authorization Server (handles authentication)
• Resource Server (API that serves protected data)
• Token Store (database for refresh tokens)
• User Identity Provider (LDAP/Active Directory)

The Authorization Server queries the Identity Provider during step 3. The Token Store is updated during step 7. The Resource Server validates tokens on each API request.

Before and After States

Before authentication:

• Client has no tokens
• User session doesn't exist
• Resource access is denied

After authentication:

• Client possesses access token (15 min lifetime)
• Client possesses refresh token (30 day lifetime)
• User session is established
• Resource access is granted with user's permissions =============== END FILE ===============

Output Specification

Create a file named auth-documentation.md that explains the authentication system in a way that would be most helpful for new engineers. Include appropriate visualizations that clarify the flow and architecture.