|
You are here |
aaronparecki.com | ||
| | | | |
philodev.one
|
|
| | | | | oAuth is a hard to get into because of its (necessary) complexity. A basic understanding of the standard flow and the actors involved can help to make better decisions and understand the security implications of the choices. | |
| | | | |
blog.doyensec.com
|
|
| | | | | Common OAuth Vulnerabilities | |
| | | | |
indieweb.org
|
|
| | | | | [AI summary] The text provides a comprehensive overview of IndieAuth, an open protocol for decentralized identity and authentication. It covers the protocol's purpose, key concepts like authorization and token endpoints, implementation examples, and related technologies. The content is structured into sections explaining the protocol's design, use cases, and practical applications. | |
| | | | |
fhirblog.com
|
|
| | | If you've read the previous posts talking about OAuth2, then (hopefully) it's clear how a user can authorize an application to retrieve their data from some server without needing to expose their login credentials. The Authorization Server is the only component that needs to have the persons username and password (or whatever authorization method is... | ||