feat: Add client credentials guide for NGINXaaS Google#2052
Open
nparikh03 wants to merge 11 commits into
Open
Conversation
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
Author
|
I have hereby read the F5 CLA and agree to its terms |
✅ Deploy Preview will be available once build job completes!
|
mjang
reviewed
Jun 17, 2026
ba34241 to
f781e89
Compare
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
There was a problem hiding this comment.
Pull request overview
This PR adds a new NGINXaaS for Google Cloud quickstart how-to guide that explains how to create and use OAuth2 client credentials for programmatic access to the NGINXaaS API (for example, automation via Terraform or CI/CD).
Changes:
- Adds a new “client credentials” guide with console-based creation/retrieval/deletion steps.
- Documents token exchange and authenticated API call examples (cURL), plus best practices and error examples.
- Adds a quick reference table summarizing limits and token/credential properties.
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
JTorreG
reviewed
Jun 17, 2026
tstraley
reviewed
Jun 17, 2026
puneetsarna
reviewed
Jun 17, 2026
puneetsarna
reviewed
Jun 17, 2026
puneetsarna
reviewed
Jun 17, 2026
puneetsarna
reviewed
Jun 17, 2026
Contributor
|
@nparikh03 : Can you please make sure to address this https://github.com/nginx/documentation/pull/2052/changes#r3431835287. I will review the rest of it for now. |
b2b0ddc to
ac27394
Compare
puneetsarna
reviewed
Jun 17, 2026
851dafc to
55d1faa
Compare
55d1faa to
c50ac20
Compare
JTorreG
reviewed
Jun 22, 2026
JTorreG
reviewed
Jun 22, 2026
Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com>
4ea1bb4 to
3fce686
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Add new how-to guide for setting up OAuth2 client credentials for programmatic access to NGINXaaS for Google APIs.
This guide covers:
Creating and managing client credentials from the NGINXaaS console
Retrieving and displaying client information
Deleting expired credentials
Exchanging client credentials for access tokens
Best practices for credential security and expiration
This enables machine users such as Terraform, CI/CD pipelines, and automation tools to authenticate securely with the NGINXaaS API.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩