Loading article...
Loading article...
Stream/Area:
-
Subject:
-
Paper ID:
IJSREM62539
Volume:
10 |
5 |
May 2026
Pages:
1-7
Publication Frequency:
Monthly (12 issues per year)
License:International Journal of Scientific Research in Engineering and Management follows the Creative Commons Attribution 4.0 (CC BY 4.0) License, allowing free use and distribution with proper attribution.
Department of Computer Science and Engineering
Sandip University, Nashik, India
Department of Computer Science and Engineering
Sandip University, Nashik, India
Department of Computer Science and Engineering
Sandip University, Nashik, India
Department of Computer Science and Engineering
Sandip University, Nashik, India
Department of Computer Science and Engineering
Sandip University, Nashik, India
YouTube creators often work with editors, managers, thumbnail designers, and other remote team members. In many small teams, collaboration still happens through informal methods such as sharing account credentials, sending final video files through cloud links, or giving broad access through platform permissions. These methods are convenient, but they create security and workflow problems. The creator may lose control over final publishing decisions, and team members may get more access than they actually need. This paper presents YouLayer, a secure video publishing middleware designed for YouTube teams. The system allows managers to upload video drafts, thumbnails, and metadata, while only the creator can review, approve, reject, and publish the final video. YouLayer uses JWT-based authentication, role-based access control, Google OAuth 2.0, AES-encrypted token storage, Backblaze B2 signed URL uploads, MongoDB Atlas, and the YouTube Data API v3. The implementation was tested using functional, integration, acceptance, and product-level testing. Results show that the system successfully supports controlled collaboration without sharing YouTube credentials. The main limitations are dependency on third-party APIs, YouTube Data API quota restrictions, hosting delays on free-tier infrastructure, and limited real-time notification support.
KEYWORDS
This paper presented YouLayer, a secure video publishing middleware for YouTube teams. The project addresses a practical problem faced by creators who work with remote managers or editors. Existing informal workflows often require credential sharing or broad channel access. YouLayer avoids this by separating draft preparation from final publishing. Managers can upload video drafts and metadata, but only creators can approve and publish content. The system was implemented using React.js, Tailwind CSS, Node.js, Express.js, MongoDB Atlas, Backblaze B2, JWT authentication, Google OAuth 2.0, AES-encrypted token storage, and the YouTube Data API v3. The architecture keeps large media files outside the backend server by using signed URL uploads. It also keeps YouTube authorization controlled through OAuth tokens stored securely on the server. Role-based access control ensures that creator-only actions cannot be performed by managers. Testing showed that the main workflows worked correctly. Authentication, invitation, manager onboarding, signed URL generation, draft submission, creator review, unauthorized access blocking, and publishing checks were validated. The results confirm that the proposed system is technically feasible and useful for small creator teams that need better control over video publishing. The project also showed some honest limitations. YouTube Data API quota limits can affect publishing, especially if the system grows. External API dependency is unavoidable because the system relies on Google, YouTube, cloud storage, and hosted infrastructure. Formal performance benchmarking was not completed, and real-time notification support is limited in the current version. These limitations do not invalidate the project, but they clearly show where future work is needed. Future work can improve YouLayer in several directions. Real-time notifications using WebSockets or push notifications should be added so that managers instantly know when submissions are approved or rejected. A background job queue can improve upload reliability and retry failed publishing tasks. Quota monitoring should be added for YouTube Data API usage so creators can see whether publishing capacity is available. Multi-factor authentication and better audit logs can improve security. A dedicated mobile application can help creators review and approve drafts from anywhere. The platform can also be extended beyond YouTube to support publishing on Instagram, Facebook, Vimeo, or TikTok, although each platform would bring its own API restrictions. Overall, YouLayer demonstrates that a secure middleware approach can reduce credential sharing and improve team-based publishing workflows. For a final year undergraduate project, it provides a complete and practical implementation of authentication, authorization, cloud upload, OAuth integration, and controlled API-based publishing.
1. D. Hardt, “The OAuth 2.0 Authorization Framework,” IETF RFC 6749, Oct. 2012. [Online]. Available: https://datatracker.ietf.org/doc/html/rfc6749 2. Google LLC, “OAuth 2.0 Best Practices for Google APIs,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://developers.google.com/identity/protocols/oauth2 3. OWASP Foundation, “A01: Broken Access Control — OWASP Top 10:2021,” 2021. [Online]. Available: https://owasp.org/Top10/A01_2021-Broken_Access_Control/ 4. Google LLC, “Using OAuth 2.0 for Web Server Applications,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://developers.google.com/identity/protocols/oauth2/web-server 5. M. Jones, J. Bradley, and N. Sakimura, “JSON Web Token (JWT),” IETF RFC 7519, May 2015. [Online]. Available: https://datatracker.ietf.org/doc/html/rfc7519 6. Backblaze Inc., “Backblaze B2 Cloud Storage S3-Compatible API,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://www.backblaze.com/apidocs/s3-compatible-api 7. Backblaze Inc., “Using Pre-Signed URLs with Backblaze B2 through S3-Compatible SDKs,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://www.backblaze.com/docs/cloud-storage-s3-compatible-api 8. Google LLC, “YouTube Data API Quota Calculator,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://developers.google.com/youtube/v3/determine_quota_cost 9. National Institute of Standards and Technology (NIST), “Advanced Encryption Standard (AES),” FIPS PUB 197, Nov. 2001. [Online]. Available: https://csrc.nist.gov/publications/detail/fips/197/final 10. Google LLC, “YouTube Data API v3 Overview,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://developers.google.com/youtube/v3 11. Google LLC, “Using OAuth 2.0 to Access Google APIs,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://developers.google.com/identity/protocols/oauth2 12. Backblaze Inc., “Backblaze B2 Cloud Storage Native API,” 2026. Accessed: Apr. 25, 2026. [Online]. Available: https://www.backblaze.com/apidocs/b2-api
Publication Date
5/5/2026
Peer Review Type
Double-Blind Peer Review
Review Rounds: 2
Documents
Article Views
0
Total views since publication
PDF Downloads
5
Total downloads since publication
Geographic Reach
5
Digital Preservation: This article is permanently archived on Zenodo and complies with all data preservation standards across major indexing platforms.
Plagiarism Screening
This manuscript has been checked for plagiarism using TurnitinPlagiarismChecker software.
Conflict of Interest
The authors declare no conflict of interest related to this research work.
Funding Information
No funding information available for this research.
Related research in the same subject area
Loading similar articles...