Skip to content
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

Docs: adds JWT opaque token note to doc #669

Merged
merged 1 commit into from
Jun 7, 2023

Conversation

ZPain8464
Copy link
Contributor

Adds a notice explaining the intended use of pomerium_jwt as an opaque token when authenticating against the API.

Fixes #662
Fixes #666

@netlify
Copy link

netlify bot commented Jun 7, 2023

Deploy Preview for pomerium-docs ready!

Name Link
🔨 Latest commit 35be16a
🔍 Latest deploy log https://app.netlify.com/sites/pomerium-docs/deploys/64809d0d9100f0000898ad34
😎 Deploy Preview https://deploy-preview-669--pomerium-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@ZPain8464 ZPain8464 marked this pull request as ready for review June 7, 2023 17:07
@ZPain8464 ZPain8464 requested a review from a team as a code owner June 7, 2023 17:07
@ZPain8464 ZPain8464 requested review from cmo-pomerium and removed request for a team June 7, 2023 17:07
@ZPain8464 ZPain8464 merged commit 4c5f868 into main Jun 7, 2023
9 checks passed
@ZPain8464 ZPain8464 deleted the zpain/update-programmatic-access branch June 7, 2023 17:08
backport-actions-token bot pushed a commit that referenced this pull request Jun 7, 2023
adds JWT opaque token note to doc
ZPain8464 added a commit that referenced this pull request Jun 7, 2023
Docs: adds JWT opaque token note to doc (#669)

adds JWT opaque token note to doc

Co-authored-by: zachary painter <[email protected]>
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.

Programmatic access documentation is not up to date JWT should not be mentioned in programmatic access
3 participants