NoMongo: Replace Base64 Storage with MinIO Client in OrgUpdate.tsx

[NishantSinghhhhh]

Problem
OrgUpdate.tsx currently uses Base64 encoding for storing images, which increases memory usage and slows down performance.

Solution
Integrate MinIO client to upload images and store only the file URLs, reducing payload size and improving efficiency.

Alternatives Considered

• Keeping Base64 (inefficient for large files).
• Using third-party storage services (MinIO provides a self-hosted alternative).

Approach

1. Remove Base64 encoding.
2. Implement MinIO file uploads and store URLs in the database.
3. Ensure proper error handling and security measures.

Additional Context
This update will optimize image storage, enhance scalability, and improve user experience.

---

NOTE

1. We recently discovered a flaw in the code base where there are some XSS and CORS vulnerabilities. This occurs when the API and Admin servers run on different machines.

2. You will notice this if you configure your Admin app on your local machine to use the API running on https://test.talawa.io/graphql.

3. The errors in your browser will look like this:

   

4. As part of this issue you will need to ensure that the browser only interacts with the API through the Admin server and never with the API directly.

[DEEPANSHI-02]

I want to work on this please @palisadoes

[palisadoes]

PTAL at the XSS and CORS vulnerabilities mentioned above that you will need to address as part of this.

[ManasiRN]

Hi @palisadoes,
I’d like to work on this issue for GSoC! I'll replace Base64 storage with MinIO, store file URLs, and address XSS/CORS vulnerabilities. Could you assign me this issue?

Thanks

[palisadoes]

We'll stick with our assignment policy.

[palisadoes]

Unassigning. 2 weeks of inactivity

[Akshat2gupta]

Hi @NishantSinghhhhh, I’d love to work on this issue! Since optimizing image storage with MinIO is a great improvement for performance and security, I’d be happy to implement the changes.

Could you please assign this issue to me? Thanks!