Feature: Google Drive Upload Integration for Scan Reports

[techmore]

Feature Request: Google Drive Upload Integration for Scan Reports

Summary

Add one-click Google Drive upload functionality to automatically backup scan reports (HTML, XML, PDF) to a dedicated "Techmore Network Scanner" folder in the cloud.

Problem Statement

Currently, scan reports are only stored locally. Users need to manually backup critical security scan data, risking data loss and making collaboration difficult.

Proposed Solution

Implement OAuth 2.0 authentication with Google Drive API for seamless cloud backup:

1. Google Drive Button: Blue Google Drive icon appears next to "Generate Report" button
2. One-Click Authorization: Click opens modal with OAuth authorization URL
3. Secure OAuth Flow: User authorizes the app (registered as "Techmore Network Scanner")
4. Automatic Setup: Creates "Techmore Network Scanner" folder on first use
5. Smart Upload: Automatically uploads HTML, XML, and PDF reports to the folder

User Experience Flow

Setup (One-time)

1. User clicks blue Google Drive icon (🚀)
2. Modal appears with "Connect to Google Drive" button
3. Button opens Google OAuth page in new tab
4. User signs in and authorizes "Techmore Network Scanner" app
5. Authorization code is returned to the app
6. App exchanges code for secure tokens (stored encrypted)

Usage (Every time)

1. After generating a report, click "Upload to Drive" button
2. Files automatically upload to "Techmore Network Scanner/YYYY-MM-DD/" folders
3. Success notification shows uploaded file links

Technical Implementation

Frontend Changes

<!-- Add Google Drive button next to Generate Report -->
<button id="upload-drive-btn" class="mt-2 inline-flex items-center justify-center gap-2 rounded-full bg-blue-600 text-white hover:bg-blue-700 font-medium py-1 px-3 text-xs transition-colors">
  <svg class="w-3 h-3" fill="currentColor" viewBox="0 0 24 24">
    <path d="M12 2C6.48 2 2 6.48 2 12s4.48 10 10 10 10-4.48 10-10S17.52 2 12 2zm-2 15l-5-5 1.41-1.41L10 14.17l7.59-7.59L19 8l-9 9z"/>
  </svg>
  Upload to Drive
</button>

Backend Implementation

• OAuth 2.0 flow with secure token storage (encrypted, not hashed)
• Google Drive API v3 integration
• Automatic folder creation: "Techmore Network Scanner/Scans/YYYY-MM-DD/"
• Upload HTML, XML, PDF files with metadata

Security Features

• Encrypted Token Storage: Uses Fernet encryption (reversible, not hash)
• User-Controlled OAuth: Users authorize their own Google account
• Registered App: "Techmore Network Scanner" appears as legitimate app in OAuth flow
• Scoped Permissions: Only requests necessary Drive permissions

Folder Structure

Google Drive Root/
└── Techmore Network Scanner/
    └── Scans/
        ├── 2026-01-09/
        │   ├── scan_report_2026-01-09_10-30-00.html
        │   ├── scan_data_2026-01-09_10-30-00.xml
        │   └── scan_report_2026-01-09_10-30-00.pdf
        └── 2026-01-10/
            ├── scan_report_2026-01-10_14-15-30.html
            └── ...

Dependencies

• google-api-python-client
• google-auth-oauthlib
• cryptography (for token encryption)
• google-api-python-client[drive] (optional, for Drive-specific features)

Acceptance Criteria

• ✅ Google Drive button appears next to Generate Report button
• ✅ One-click OAuth authorization flow
• ✅ "Techmore Network Scanner" folder auto-created
• ✅ HTML, XML, PDF files upload automatically
• ✅ Files organized by date in subfolders
• ✅ Encrypted token storage (no plaintext credentials)
• ✅ Error handling for network/API issues
• ✅ Success notifications with file links
• ✅ Disconnect/revoke authorization option

Benefits

• Zero-Config Backup: One-click setup, automatic uploads
• Data Safety: Cloud backup prevents local data loss
• Collaboration: Share scan results via Google Drive links
• Professional UX: Seamless integration feels native
• Security: Encrypted storage, OAuth best practices

Priority

High - Immediate value for data persistence and user experience.

Related Issues

None at this time.

[techmore]

Google Drive Integration Audit & Implementation Plan

Current Status

✅ Completed:

• Google Drive API integration with OAuth flow
• Encrypted token storage using Fernet encryption
• Automatic folder creation (Techmore Network Scanner/Scans/YYYY-MM-DD/)
• Flask routes for auth, upload, and status checking
• Basic upload button in UI
• Dependencies added to requirements.txt

❌ Issues Found:

• OAuth flow broken for web apps (uses desktop "oob" flow incorrectly)
• No Google Drive icon on button (shows checkmark)
• No auto-upload after report generation
• Manual auth process is clunky (user must handle popup flow)
• No connection status indicator in UI

Security Audit

✅ Good:

• Tokens encrypted with Fernet (AES-based)
• State verification in OAuth flow
• HTTPS requirement for API calls

⚠️ Concerns:

• Client ID/Secret temporarily stored in frontend during auth
• No token refresh handling (Google tokens expire)
• File paths passed from frontend without validation

Implementation Plan

Phase 1: Fix OAuth Flow (2-3 hours)

• Update OAuth flow to use proper web redirect URI
• Implement popup window handling with completion polling
• Add proper error handling for auth failures

Phase 2: UI Improvements (1-2 hours)

• Replace checkmark with Google Drive icon
• Add connection status indicator
• Improve auth modal UX

Phase 3: Auto-Upload Integration (1 hour)

• Hook into report generation completion
• Auto-upload HTML, XML, and PDF files when Drive is connected
• Add upload progress feedback

Phase 4: Security Hardening (1-2 hours)

• Validate file paths on backend
• Implement token refresh logic
• Clear sensitive data from frontend after auth

Phase 5: Testing (2-3 hours)

• Test OAuth flow end-to-end
• Verify auto-upload functionality
• Test error scenarios and edge cases

Acceptance Criteria

• OAuth flow works seamlessly in web browser
• Google Drive icon button shows connection status
• Reports auto-upload after generation when connected
• Manual upload button works for additional files
• Security best practices implemented
• Error handling graceful and user-friendly

Estimated Total Effort: 7-11 hours

The foundation is solid but needs the OAuth flow completion and UI polish to be production-ready.

[techmore]

Update: We need to publish the OAuth app in Google Cloud Console to 'In production' status so users can authenticate without the 'unverified app' approval process. This will allow seamless OAuth clicks without manual app approvals.