-
Notifications
You must be signed in to change notification settings - Fork 367
Add section for api token security [SECFEAT-1021] #3921
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
Conversation
@salolivares when you get an exact date for when this is being shipped to production, can you let me know? Want to make sure this goes out on the right date. Thanks! |
@stayseesong will do! We're aiming for a early January release. I'll ping once we figure out a hard date. |
a469d56
to
26649c7
Compare
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: stayseesong <[email protected]>
26649c7
to
a61448e
Compare
@stayseesong the feature is going live! when can we have the docs published? |
@salolivares when is it going live? |
@stayseesong this feature is live now! (1/17) |
@salolivares ok! will get the docs to deploy today |
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
This PR adds a section under the public api page in order to describe a new feature that is being rolled out (exposed papi token service, see sdd here).
Merge timing
This depends on https://github.com/segmentio/exposed-papi-token-service being shipped to production. We're aiming for an early January release.