Week 4: Expanding Secure Functions in LodgingFlow

 OJT Weekly Narrative – Week 4

July 1 – July 5, 2025
Christian M. Lagarde – 3rd Year Computer Science Student

Securing New Functions: LodgingFlow Expansion

Week 4 centered on extending the backend functionality of the LodgingFlow project while maintaining strict adherence to our security and architecture standards. With the core authentication and encryption systems already in place, I focused on adding new API functions and database collections, each designed with CORS policies, AES encryption/decryption, and Firebase authentication baked into their logic.

The goal was not just expansion—it was secure scalability. Every new function I created had to validate authenticated requests, properly decrypt incoming payloads, and return encrypted responses when applicable. I also ensured that new routes were CORS-compliant, allowing controlled frontend access from verified origins.

Function by Function: Growing the API

Each day brought a new collection or function. I added endpoints that interacted with key backend services, following REST principles while also layering in Firebase role-based authentication checks to control data access.

The Postman workspace became my testing ground. I used it to simulate various roles, verify encrypted payloads, and inspect CORS headers in real time. This methodical testing ensured every function responded with the correct status codes and securely handled both valid and invalid requests.

Backend Discipline, Frontend Awareness

Although I remained focused on backend tasks, the importance of frontend integration was always in view. I designed all new endpoints to be easily consumable by our upcoming UI, returning clean data models and ensuring proper token validation. I paid attention to response structure, error consistency, and timeout handling, knowing these would affect frontend behavior.

Reflection: Secure Growth, Not Just Expansion

What defined this week wasn’t just the number of endpoints added, but the consistent application of secure development practices. With every new feature, I applied the same standards I established in earlier weeks: encrypt data, validate tokens, enforce CORS, and return precise, predictable results.

Through this process, I gained a deeper appreciation for maintainable growth in backend systems—where every new piece doesn’t just work, but fits into a secure, scalable, and reliable whole.

Completed Highlights

  • Added new functions and database collections in the LodgingFlow backend

  • Integrated Firebase authentication checks on all new routes

  • Ensured CORS compliance across every new endpoint

  • Applied AES encryption/decryption to request and response handling

  • Validated all functions using Postman with both valid and invalid tokens

  • Maintained consistent HTTP status codes and error handling patterns

End of Week 4 Narrative

Comments

Popular posts from this blog

Week 2: Refactoring and Cloud Integration

Week 1: Orientation and Onboarding

Week 7: Frontend Fixes and Collaborative Admin Panel Design