Skip to content

[ZT] Use Access service token in one header #22035

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

Merged
merged 2 commits into from
Apr 30, 2025

Conversation

ranbel
Copy link
Contributor

@ranbel ranbel commented Apr 28, 2025

PCX-16792

Copy link
Contributor

hyperlint-ai bot commented Apr 28, 2025

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 Summary

Enhanced service token authentication by allowing the use of a single HTTP header for access, improving compatibility with SaaS services.

  • Introduced the option to authenticate using a single HTTP header for service tokens.
  • Updated documentation to include instructions for configuring the self-hosted Access application.
  • Provided an example of using the new authentication method with curl.

Modified Files

  • src/content/docs/cloudflare-one/identity/service-tokens.mdx

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 hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

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 hyperlint-ignore to the PR to ignore the link check for this PR.

json={{
"domain": "app.example.com",
"type": "self_hosted",
"read_service_tokens_from_header": "Authorization"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add an ellipses or something to simulate adding all the other fields. I think be default this would remove most of them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The APIRequest Markdown component does not support adding ellipses. Proposed workaround: cd7dd28

@ranbel ranbel requested a review from jroyal April 29, 2025 15:19
@ranbel ranbel merged commit 7bd5c0e into production Apr 30, 2025
13 checks passed
@ranbel ranbel deleted the ranbel/access-service-token-header branch April 30, 2025 19:09
GregBrimble pushed a commit that referenced this pull request May 1, 2025
* send service token in one header

* clarify PUT request body
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants