Authorize, don't authenticate
blog.marcua.net
Authorize, don't authenticate
1–10 of 48 posts
Re: Authorize, don't authenticate
#2We are back to File->Open I guess. We could use native applications instead of web apps while we're at it.
Sadly this approach does not work for a lot of (web) apps.
Re: Authorize, don't authenticate
#3Not sure this does anything for data portability, since apps will just store the data as encrypted & signed BLOBs.
Re: Authorize, don't authenticate
#41. How do you get around performance issues? If I have a difficult join and you have a slow database, or you have a flaky connection, how can I debug the problem on my end?
2. What stops me (or any attacker) from exploiting your lack of security? Are you 100% sure you are secure?
3. You mention collaboration - How does this work at a company level if we have many users and need to control access - the company is the entity with rights to the data in this case.
Re: Authorize, don't authenticate
#5So many tools and libraries combine authorization and authentication, and it’s hard to find an authorization server that lets you outsource identity.
(All too often the underspecified abbreviation “auth” is used to cover both.)
Shameless plug: My colleagues and I implemented a minimal authorization server that lets you leverage a trusted identity provider of your choice (like Entra ID or even Auth0/Okta) and handle authorization. It looks up what roles and permissions the identified user should be able to have/grant and issues tokens containing that authorization.
Re: Authorize, don't authenticate
#6So many tools and libraries combine authorization and authentication, and it’s hard to find an authorization server that lets you outsource identity. (All too often the underspecified abbreviation “auth” is used to cover both.) Shameless plug: My colleagues and I implemented a minimal authorization server that lets you leverage a trusted identity provider of your choice (like Entra ID or even Auth0/Okta) and handle a…
Nice! If it works with Authelia (or Authentik) too then I'm sold. Thanks for sharing.
Re: Authorize, don't authenticate
#7We are back to File->Open I guess. We could use native applications instead of web apps while we're at it. Sadly this approach does not work for a lot of (web) apps.
yeah, to me this also pretty much sounds like the approach we started with, we bring our data (as a file) into the application and it stores it back if we want to.
Re: Authorize, don't authenticate
#8Got drawn to the topic, however usage of authentication and authorization seem like misnomer here, the core topic seems to be data ownership
The concept on a surface level to have ownership over the data makes a lot of sense and to a large part the support exists in a fragmented manner across the different providers/applications.
The concrete idea of user having a database and then authorizing that to the service is highly impractical. It might be applied for experimentation purposes in highly controlled environment but cant scale beyond that.
1. Databases require maintenance, backups, failover
2. Schema update are nightmares. No one is ever comfortable with it, specially the bigger you are.
3. Authorization seems to be following one to many pattern here, one database and multiple applications. Its a no go in case of update operations
Re: Authorize, don't authenticate
#9Got drawn to the topic, however usage of authentication and authorization seem like misnomer here, the core topic seems to be data ownership The concept on a surface level to have ownership over the data makes a lot of sense and to a large part the support exists in a fragmented manner across the different providers/applications. The concrete idea of user having a database and then authorizing that to the service is…
yeah the article is dumb.
Re: Authorize, don't authenticate
#10Isn't this the core idea behind atproto?