You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/discord-social-sdk/core-concepts/oauth2-scopes.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,12 +62,12 @@ See [available OAuth2 scopes](/docs/topics/oauth2#shared-resources-oauth2-scopes
62
62
63
63
## OAuth2 Client Types
64
64
65
-
OAuth2 has two client types: **Public** and **Confidential**. Most games will not want to ship with **Public Client** enabled.
65
+
OAuth2 has two client types: **Confidential** and **Public**. Most games will not want to ship with **Public Client** enabled.
66
66
67
67
Some Social SDK methods require your Discord application to be a **Public Client**. These methods also have server-side alternatives that you can use with a **Confidential Client**.
68
68
69
-
- Public clients cannot securely store client secrets.
70
69
- Using confidential clients with proper secret management for production applications is generally recommended.
70
+
- Public clients cannot securely store client secrets.
71
71
- Your security team should review this setting and authentication flows before releasing your game.
72
72
73
73
[Learn more about OAuth2 client types](https://oauth.net/2/client-types)
Copy file name to clipboardExpand all lines: docs/discord-social-sdk/development-guides/account-linking-with-discord.mdx
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,25 +108,6 @@ Once the user approves the request from Step 2, Discord will redirect the user b
108
108
109
109
#### Token Exchange for Public Clients
110
110
111
-
<PublicClient />
112
-
113
-
If your app does not have a backend server, enable `Public Client` in the Discord Developer Portal and use [`Client::GetToken`] to automatically exchange the authorization code for a token.
114
-
115
-
We will also need the code verifier used to generate the code challenge in Step 1.
// Next step: Update the token in the client and connect to Discord
127
-
});
128
-
```
129
-
130
111
#### Server-to-Server Get Token Exchange
131
112
132
113
If your application uses a backend server and does **not** have `Public Client` enabled, you can manually exchange the authorization code for an access token using the Discord API.
If your app does not have a backend server, enable `Public Client` in the Discord Developer Portal and use [`Client::GetToken`] to automatically exchange the authorization code for a token.
149
+
150
+
We will also need the code verifier used to generate the code challenge in Step 1.
0 commit comments