Contact person: Business Client

Phone:Show

Email:Show

Location: Lanús, Argentina

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Technical Requirement – Web Application
1. Authentication
The project must implement a robust authentication system with support for professional accounts and LinkedIn.
The authentication flow must include:
1.1. Login Providers
LinkedIn OAuth


Google Workspace OAuth (corporate Google accounts)


Azure AD OAuth (corporate Microsoft accounts)


Auth0 (OIDC) as a universal fallback provider


Session persistence in the browser (secure cookies + JWT)


1.2. Automatic User Creation
When a user logs in for the first time:
A new user record must be created in the database


The user must be automatically assigned to the free_trial plan


The authentication provider must be stored


The last login timestamp must be updated


1.3. Login Notifications
Every time a user logs in (first-time or returning), an email notification must be sent to the configured admin inbox.

2. Full Database Integration
The web application must be fully connected to the provided SQL database, including:
Creation and management of users, organizations, memberships, and invitations


Validation of the free_trial plan limits using the existing SQL functions


Uploading files associated with users or organizations


Handling report states according to the defined schema


Payment and upgrade logic will not be implemented yet, but the system must be prepared for seamless integration in the future.

3. Email (EmailJS)
An email must be sent when someone submits the contact form


An email must be sent when a user logs in


Templates already exist; the developer only needs to integrate the credentials



4. Invitation Management
The full invitation flow must be implemented:
Token generation


Sending the invitation email


Token validation


Assigning the user role upon acceptance


Ability to mark an organization as the user's primary org


Token expiration handling



5. VirusTotal File Scanning
Every uploaded .pbit file must follow this security flow:
Temporary upload


Submit file to the VirusTotal API


Approve or block based on the result


Log the scan status inside the database


This must be integrated into the existing upload flow.

6. Current Project Status
The web application is already advanced, with:
Structured and functional frontend


Completed design system


Fully designed database schema, stored procedures, and SQL functions


The developer must:
Integrate backend, authentication, and database


Connect real endpoints


Implement the full logical flows and forms


Prepare the system for production deployment



7. Credentials
The client already has all required credentials:
OAuth (Google, Azure AD, LinkedIn, Auth0)


EmailJS


Azure SQL


VirusTotal API


All credentials will be provided for integration.

Final Summary
The final deliverable should include:
A solid enterprise-grade authentication system


Fully functional SQL database integration


Operational contact form


Login notification system


Complete invitation workflow


VirusTotal file scanning integrated into the upload process


Everything must be implemented in a stable manner and prepared for future extensions such as paid plans and advanced account features.



Technology Stack
8.1 Current Stack (Frontend – Already Implemented)
Frontend Framework
React 18.2.0 – UI principal


Vite 7.2.2 – Build tool y servidor de desarrollo


React Context API – Manejo de estado global (AuthContext, OrganizationContext)


CSS3 – Estilos mediante archivos CSS por componente


Current Dependencies
@azure/storage-blob (12.17.0) – Integración con Azure Blob Storage


@emailjs/browser (4.4.1) – Envío de mails vía EmailJS desde el front


Project Structure
src/
├── components/ # React components (modals, panels, forms)
├── contexts/ # AuthContext, OrganizationContext, etc.
├── hooks/ # Custom hooks
├── services/ # Integraciones (Azure Storage, EmailJS)
└── [login to view URL] # Root component

Deployment
Docker con multi-stage build


Nginx para serving de archivos estáticos


Configurado para despliegue productivo



8.2 Recommended Backend Stack
Actualmente el proyecto es solo frontend.
Para hacerlo funcional es necesario implementar un backend encargado de:
Manejar OAuth y callbacks


Gestionar operaciones con Azure SQL


Emitir y validar JWT


Exponer API REST


Procesar archivos antes de enviarlos a VirusTotal


Controlar lógica de invitaciones, usuarios, organizaciones, suscripciones y límites de plan


Recommended Backend Framework: Node.js + Express" (client-provided description)