Fix and Complete GitHub/Google Authentication and Storage Integration

[DevOlabode]

Fix and Complete GitHub/Google Authentication and Storage Integration

Description

Users can currently sign in using either GitHub or Google and choose where their scanned website data should be stored—either in a GitHub repository or a Google Drive folder. While the frontend implementation is functioning as expected, the backend integration is incomplete and does not reliably support these workflows.

This issue aims to ensure that authentication, authorization, repository/folder creation, permissions, and data storage operations work correctly end-to-end.

Scope

• Verify and fix GitHub OAuth authentication flow.
• Verify and fix Google OAuth authentication flow.
• Ensure authenticated user information is correctly retrieved and persisted.
• Ensure users can successfully create and connect a GitHub repository for storing scan results.
• Ensure users can successfully create and connect a Google Drive folder for storing scan results.
• Validate that scan results are saved to the selected storage destination.
• Improve error handling, logging, and edge-case handling throughout the integration.
• Ensure proper token management, refresh logic (where applicable), and secure storage of credentials.

Acceptance Criteria

• Users can successfully sign in with GitHub.
• Users can successfully sign in with Google.
• User sessions remain valid and are handled securely.
• GitHub repository creation works reliably.
• Google Drive folder creation works reliably.
• Scan results can be saved to the user's selected GitHub repository.
• Scan results can be saved to the user's selected Google Drive folder.
• Appropriate error messages are returned when authentication or storage operations fail.
• Backend endpoints are tested and documented.
• No frontend changes are required for the core functionality to work.