---
title: "Comment by OneLifeVibe on \"Authentication vs Authorization: What AI-Built Apps Often Get Wrong\" | Hashnode"
description: "The point about a valid token not being meant for your app is the part I would underline. It is easy to treat a successful login as proof that the request is sa"
url: "https://hashnode.com/posts/authentication-vs-authorization-what-ai-built-apps-often-get-wrong/6afc03dbc3f7cd957ce3e7f5/comment/6afc19474203073b5bfad85b"
---

[Discussion](https://hashnode.com/posts/authentication-vs-authorization-what-ai-built-apps-often-get-wrong/6afc03dbc3f7cd957ce3e7f5)

Comment [Authentication vs Authorization: What AI-Built Apps Often Get Wrong](https://hashnode.com/posts/authentication-vs-authorization-what-ai-built-apps-often-get-wrong/6afc03dbc3f7cd957ce3e7f5)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[8h ago](https://hashnode.com/posts/authentication-vs-authorization-what-ai-built-apps-often-get-wrong/6afc03dbc3f7cd957ce3e7f5/comment/6afc19474203073b5bfad85b)

The point about a valid token not being meant for your app is the part I would underline. It is easy to treat a successful login as proof that the request is safe, and then skip the checks that actually decide what the user may do. I also liked the reminder to validate permissions on the backend on every request, not only in the interface. Hiding a button is not a security control. Reading every change an AI coding agent makes, the way you describe, is the right habit here, because these are exactly the gaps that look finished at first glance.

[Aashish Panthi](https://hashnode.com/@aashishpanthi)

[7h ago](https://hashnode.com/posts/authentication-vs-authorization-what-ai-built-apps-often-get-wrong/6afc03dbc3f7cd957ce3e7f5/comment/6afc19474203073b5bfad85b#reply-6afc2a98e43409abca718b52)

Thanks! Yes, the issuer and audience check was the part I’d skipped before too. Easy to miss when the login already works.
