[ZT] Use Access service token in one header #22035
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryEnhanced service token authentication by allowing the use of a single HTTP header for access, improving compatibility with SaaS services.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
| json={{ | ||
| "domain": "app.example.com", | ||
| "type": "self_hosted", | ||
| "read_service_tokens_from_header": "Authorization" |
There was a problem hiding this comment.
We should add an ellipses or something to simulate adding all the other fields. I think be default this would remove most of them.
There was a problem hiding this comment.
The APIRequest Markdown component does not support adding ellipses. Proposed workaround: cd7dd28
|
Preview URL: https://cd7dd282.preview.developers.cloudflare.com Files with changes (up to 15) |
* send service token in one header * clarify PUT request body
* send service token in one header * clarify PUT request body
* send service token in one header * clarify PUT request body
* send service token in one header * clarify PUT request body
3 participants
PCX-16792