fix(api): resolve the CSRF vs WebSocket handshake conflict

[cypriannwokolo2-creator]

Summary

Browsers cannot set an X-CSRF-Token header on a WebSocket upgrade; csrf.go:23-29 CSRFTokenValidator requires it for upgrades on /ws, so legitimate browser WS connections may be blocked.

Acceptance Criteria

• Allow WS upgrade with a suitable auth mechanism (e.g. token query/header, Origin check)
• Keep CSRF protection for state-changing HTTP
• Integration test of browser-style WS connect

Complexity

High.

[Anieblin]

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

Hello Maintainer, I'd love to work on this issue

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

[Ade-Pheebs]

@Ade-Pheebs has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hi maintainer, kindly assign me to this issue. i would be able to resolve the CSRF vs WebSocket handshake conflict. Thank you.

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

[FICKSONPRO]

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

dug into this issue and I'm confident about the fix. I've handled similar issues before, and my approach would be to keep the change minimal and well-tested so review is quick and painless.

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

[Ennyhorla1]

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

i would like to work on this kindly assign me

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

[dorismaduegbunam]

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

Gm Chief, I would love to take on this issue. I'm a software engineer with over four years experience and i'm confident I can resolve this issue

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

[drips-wave]

Congratulations, @dorismaduegbunam! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @dorismaduegbunam: 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 🌊

[cypriannwokolo2-creator]

Fixed: WebSocket now uses WebSocketAuthMiddleware which accepts JWT from Authorization header OR ?token= query parameter. CSRF middleware removed from WS route (browser same-origin policy + Origin header check handle CSRF).

[drips-wave]

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

😎 @dorismaduegbunam: 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.