-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SUPPORTENG-482] Doc update: Update OAuth2 snippet to note key limitations #589
[SUPPORTENG-482] Doc update: Update OAuth2 snippet to note key limitations #589
Conversation
…d or client_secret as keys
packages/cli/README.md
Outdated
// in `bundle.authData` for future use. Note, `client_id` and `client_secret` | ||
// are reserved and cannot be used as keys for input form fields. | ||
// If you need to save/use something that the user shouldn't need to type/choose, | ||
// add a "computed" field, like: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you move this change to README-source.md
and let the pre-commit hook auto generate README.md
for us? Thanks!
packages/cli/package-lock.json
Outdated
"integrity": "sha512-/0V5q0WbslqnwP91tirOvldvYISzaqhClxzyUKXYxs07yUILIs5jx/k6CFe8bvKSkds5w+eiOqta39Wk3WxdcQ==" | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
package-lock.json
should not be in this change. We should undo the change here.
@eliangcs, thank you for the suggestions! I believe I've made the necessary changes, but please let me know if anything is still incorrect. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks!
Here, I've updated the OAuth2 snippet to note that
client_id
andclient_secret
can't be used as keys for form input fields.In testing, documented in the Slack threads linked in the accompanying Jira ticket, it appears
client_id
in particular conflicts with the similarly named environment variable, causing issues in the token request. This can be avoided by refraining from using these key names in input form fields in the OAuth2 config.Note: