[BE-29] Build IP allowlist and blocklist middleware

[mftee]

Overview

Let admins restrict or block access from specific IPs or CIDR ranges inside backend/cmmty/.

Acceptance Criteria

• Create backend/cmmty/ip-filter/ with middleware, module, and admin endpoints
• IpRule entity: id, cidr, type (ALLOW or BLOCK), reason, createdAt
• Implement POST and DELETE /cmmty/admin/ip-rules
• Middleware blocks requests from blocked IPs before reaching controllers
• Support CIDR notation (e.g. 192.168.1.0/24)
• Write unit tests for IP matching logic

Contribution Folder

All files must be placed inside backend/cmmty/. Do not modify any file outside this folder.

How to Contribute

Comment on this issue to express interest, fork the repo, build inside backend/cmmty/ only, and open a PR targeting main.

[Ekenesamuel8]

@Ekenesamuel8 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Can I please work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ekenesamuel8 to this issue.

[naijadatagirl]

@naijadatagirl has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello,

I’d like to work on Issue #355 in the SMALDA repository. Implementing an IP allowlist/blocklist system is a strong security enhancement and fits well with backend access control requirements.

My approach will be to build a dedicated backend/cmmty/ip-filter/ module containing the middleware, service logic, and admin endpoints. I will implement the IpRule entity with CIDR support and ensure correct handling of both ALLOW and BLOCK rules, including proper precedence logic. The middleware will intercept requests early in the lifecycle to prevent unauthorized access before reaching controllers.

I will also implement POST and DELETE endpoints for /cmmty/admin/ip-rules, and add comprehensive unit tests to validate IP matching, CIDR parsing, and edge cases.

All changes will strictly remain within the backend/cmmty/ directory as required, and I will ensure clean, secure, and well-tested implementation.

Best regards,
Naijadatagirl

ℹ️ Repo Maintainers: To accept this application, review their application or assign @naijadatagirl to this issue.

[AbuJulaybeeb]

@AbuJulaybeeb has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi Maintainer,
I would like to take on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AbuJulaybeeb to this issue.

[Cedarich]

@Cedarich has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello maintainer, please can i take up this task

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Cedarich to this issue.

[drips-wave]

Congratulations, @Cedarich! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Cedarich: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Cedarich as part of the Stellar Wave Program's 4th Wave 🥳

😎 @Cedarich: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.