How drkno/plexsso works
Main Components
a. Core Components:
• Nginx Reverse Proxy (External)
• PlexSSO Backend (ASP.NET Core)
• React Frontend (UI)
• Plex Authentication Service (External)
• Plugin System
• Target Services (External)
b. Key Architectural Elements:
• Authentication Flow
• Plugin Architecture
• Configuration Management
• Access Control System
[User Browser] → [Nginx Reverse Proxy]
[Frontend (React)]
• ↕
[Backend (ASP.NET Core)]
• ↙ ↓ ↘
[Auth] [Config] [Plugins]
[Plex Auth] [Target Services (Ombi, Deluge, etc.)]
Component Details
Frontend (UI):
• Main components: Login Page, Admin Page, Access Denied Page
• Plex OAuth integration
Backend:
• Controllers: Login, Logout, SSO, Redirect
• Services: Authentication, Configuration, Plugin Management
• Models: API models, Internal models, Type definitions
Plugin System:
• Plugin interface
• Available plugins (Deluge, Ombi, Overseerr, Tautulli)
• Plugin communication paths
Data Flow Indicators
• Authentication flow from user → Nginx → PlexSSO → Plex
• Token management between PlexSSO and target services
• Configuration data flow
• Plugin communication paths
Important Details
Authentication Flow:
Browser → Nginx auth_request → PlexSSO → Plex Authentication
• ↙
Success/Denial Response
Plugin Architecture:
[Core Service Registry]
• ↓
[Plugin Interface (IPlugin)]
• ↙ ↓ ↘
[Deluge] [Ombi] [Other Plugins]
Configuration System:
[Config Service]
• ↓
[Access Controls] → [Rule Evaluation]
Technical Details to Highlight
• ASP.NET Core backend architecture
• React frontend component structure
• Plugin system extensibility
• Configuration management
• Authentication token flow
Remember to include notes about:
• Docker deployment context
• Nginx integration requirements
• Plugin extensibility points
• Configuration options
• Security boundaries
This will provide a complete picture of how PlexSSO operates as a single sign-on solution for Plex-based services.