Add secure/brand auth in production doc #341
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
evantahler
requested changes
Jul 10, 2025
Contributor
evantahler
left a comment
evantahler
left a comment
There was a problem hiding this comment.
The only blocking thing would be to pre-make the github discussion and get that URL in here
Comment on lines
+62
to
+75
| <Tabs items={["REST"]} storageKey="preferredLanguage"> | ||
| <Tabs.Tab> | ||
| ```text | ||
| POST https://cloud.arcade.dev/api/v1/oauth/confirm_user | ||
| Authorization: Bearer <arcade_api_key> | ||
| Content-Type: application/json | ||
|
|
||
| { | ||
| "flow_id": "<flow_id from the query string>", | ||
| "user_id": "<the current user's ID>" | ||
| } | ||
| ``` | ||
| </Tabs.Tab> | ||
| </Tabs> |
Contributor
There was a problem hiding this comment.
We will get this into the client libs soon, yes?
Collaborator
Author
There was a problem hiding this comment.
Yes, next on my list. That will result in more tabs here
Comment on lines
+120
to
+121
| In the Arcade Dashboard, pick the **Custom verifier** option and add the URL of your verifier route. | ||
|
|
Contributor
There was a problem hiding this comment.
TODO: Add screenshot soon
Collaborator
There was a problem hiding this comment.
nit: if This will be under a menu item, let's expand it!
Suggested change
| In the Arcade Dashboard, pick the **Custom verifier** option and add the URL of your verifier route. | |
| In the Arcade Dashboard, go to **OAuth > Custom verifier** option, and add the URL of your verifier route. | |
Collaborator
Author
There was a problem hiding this comment.
@torresmateo Will do, I will update this after the Dashboard ships.
Co-authored-by: Evan Tahler <[email protected]>
…g-oauth-sec-docs' into nate/customer-facing-oauth-sec-docs
Collaborator
Author
|
@evantahler, back over to you! |
evantahler
approved these changes
Jul 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a doc explaining how to configure session verification for production.