Skip to content

Commit 16e8e33

Browse files
authored
Update +page.markdoc
1 parent a52851b commit 16e8e33

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/routes/blog/post/understand-oauth2/+page.markdoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ unlisted: true
1111
category: product
1212
---
1313

14-
In today’s interconnected app ecosystem, users expect seamless, secure access across services. OAuth2 has emerged as the industry standard for handling secure delegated access, making it a critical protocol for developers to understand.
14+
Modern applications rarely operate in isolation. Whether it's logging in with Google or sharing data with a third-party service, users demand interoperability and security. That’s where OAuth2 steps in: a powerful protocol designed to delegate access without compromising user credentials.
1515

1616
This guide explains OAuth2, how it works, the different flows available, and when to use each one, helping you build secure, scalable authorization experiences.
1717

@@ -42,7 +42,7 @@ Refer to the OAuth2 [documentation](/docs/product/auth/oauth2) for complete tech
4242

4343
1. **Authorization request**: The client asks the resource owner for permission.
4444
2. **Authorization grant**: If the user consents, the server issues a grant (authorization code, token, etc.).
45-
3. **Token request**: The client exchanges the grant for an access token.
45+
3. **Token request**: The client exchanges the grant for an access [token](/docs/products/auth/tokens).
4646
4. **Resource access**: The client uses the token to access protected resources.
4747

4848
Tokens are typically short-lived and scoped, meaning they only allow the operations the user approved.
@@ -68,7 +68,7 @@ OAuth2 offers different "flows" to accommodate various scenarios. Here's a break
6868

6969
- Web apps with secure backend servers.
7070

71-
{% call_to_action title="Customer identity without the hassle" description="Add secure authentication for your users in just a couple of minutes." point1="Multiple OAuth providers" point2="Built-in security" point3="Custom roles and permissions" point4="Integrates with your favourite SDK" cta="Contact sales" url="https://appwrite.io/contact-us/enterprise" /%}
71+
{% call_to_action title="Customer identity without the hassle" description="Add secure authentication for your users in just a couple of minutes." point1="Multiple OAuth providers" point2="Built-in security" point3="Custom roles and permissions" point4="Integrates with your favourite SDK" cta="Request a demo" url="https://appwrite.io/contact-us/enterprise" /%}
7272

7373

7474
## 2. Authorization code flow with PKCE (Proof Key for Code Exchange)

0 commit comments

Comments
 (0)