Add structured log for auth token validation failure on protected routes

[Chucks1093]

Summary
When an auth token fails validation on a protected route, the 401 response is returned to the client but no structured log is emitted. A warn-level log at the validation failure point helps distinguish expired tokens from malformed ones without exposing the token value.

Scope

• identify where auth token validation occurs for protected routes
• add a warn-level structured log on validation failure
• include the failure reason, route path, and request ID but not the token value

Acceptance Criteria

• a token validation failure emits a warn-level log with reason, route, and request ID
• the token value is not present in the log
• the client 401 response is unchanged

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[chinecherem58]

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

hi maintainer i will like to work on this issue

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

[Priyanshu1-62]

@Priyanshu1-62 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi @Chucks1093,
I would like to work on this issue. Can you please assign it to me? Thank you.

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

[victor62-art]

@victor62-art has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

pls assign me to this issue

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

[Vvictor-commits]

@Vvictor-commits has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

please assign this issue to me

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

[khanavi272-spec]

@khanavi272-spec has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue

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

[drips-wave]

Congratulations, @victor62-art! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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