---
title: "Comment by netproxy on \"Securing Apps: Password Hashing, RBAC, OAuth, and OpenID Connect\" | Hashnode"
description: "The layered structure works well: starting with password hashing, then moving to RBAC, and finally to OAuth and OpenID Connect makes the difference between auth"
url: "https://hashnode.com/posts/securing-apps-password-hashing-rbac-oauth-and-openid-connect/6aea19761b452a285d3b6b23/comment/6aea73967535228956fdb201"
---

[Discussion](https://hashnode.com/posts/securing-apps-password-hashing-rbac-oauth-and-openid-connect/6aea19761b452a285d3b6b23)

Comment [Securing Apps: Password Hashing, RBAC, OAuth, and OpenID Connect](https://hashnode.com/posts/securing-apps-password-hashing-rbac-oauth-and-openid-connect/6aea19761b452a285d3b6b23)

[netproxy](https://hashnode.com/@argumentmoney8117)

[Nov 3](https://hashnode.com/posts/securing-apps-password-hashing-rbac-oauth-and-openid-connect/6aea19761b452a285d3b6b23/comment/6aea73967535228956fdb201)

The layered structure works well: starting with password hashing, then moving to RBAC, and finally to OAuth and OpenID Connect makes the difference between authentication and authorization much clearer.
