Skip to content

Commit b559dbb

Browse files
committed
update oauth info for authentication
1 parent cdc02d9 commit b559dbb

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

settings/authentication-personalization/authentication-setup/choosing-a-handshake.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Before your users can access personalized content, they must be authenticated. M
2828
</Tab>
2929
<Tab title="OAuth 2.0">
3030

31-
- You have an existing OAuth server that supports the PKCE flow.
31+
- You have an existing OAuth server that supports the Authorization Code flow.
3232
- You can create a new API endpoint that can be accessed by the returned OAuth access token.
3333
</Tab>
3434
<Tab title="Mintlify Dashboard">

settings/authentication-personalization/authentication-setup/oauth.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: 'OAuth 2.0 Handshake'
3-
description: 'Integrate with your OAuth server to enable user login via the PKCE flow'
3+
description: 'Integrate with your OAuth server to enable user login via the Authorization Code flow'
44
---
55

66
<Info>
@@ -35,7 +35,7 @@ If you have an existing OAuth server, you can integrate with Mintlify for a seam
3535

3636
## Example
3737

38-
I have an existing OAuth server that supports the PKCE flow. I want to set up authentication for my docs hosted at `foo.com/docs`.
38+
I have an existing OAuth server that supports the Authorization Code flow. I want to set up authentication for my docs hosted at `foo.com/docs`.
3939

4040
To set up authentication with Mintlify, I create an endpoint `api.foo.com/docs/user-info` which requires an OAuth access token with the `docs-user-info` scope, and responds with the user's custom data according to Mintlify’s specification.
4141

0 commit comments

Comments
 (0)