Repository navigation
Document write-only provider secret keys and the Origin header for server submissions - #216
Merged
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
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.
The API reference says provider secret keys stay in the dashboard, which formspark/monorepo#353 changes. The allowed domains section also says every server submission fails. This PR documents the four write-only key fields and the single-use challenge response. It also states that a server submission passes with an Origin header that names an allowed domain.
Merge this PR only after the monorepo deploy of #353 is green, since the docs describe the new API. The pages for the dashboard setup steps do not change.