Skip to content

Fix wording: NGTS stands for Security, not Services #2140

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.

Sign up for GitHub

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

Open
maelvls wants to merge 1 commit into
base: release-next
Choose a base branch
from
+12 −9
Open

Fix wording: NGTS stands for Security, not Services #2140

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 12 additions & 9 deletions content/docs/configuration/venafi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,10 @@ description: 'cert-manager configuration: CyberArk Issuers'

## Introduction

The CyberArk `Issuer` obtains certificates from
[CyberArk Certificate Manager](https://www.cyberark.com/products/certificate-manager/) SaaS or Self-Hosted,
or from [Palo Alto Networks Next Generation Trust Services (NGTS)](https://www.paloaltonetworks.com/sase).
The CyberArk `Issuer` obtains certificates from [CyberArk Certificate
Manager](https://www.cyberark.com/products/certificate-manager/) SaaS or
Self-Hosted, or from [Palo Alto Networks Next-Generation Trust Security
(NGTS)][ngts].

The `Issuer` was formerly known as the Venafi `Issuer`, and for backwards compatibility reasons is configured using older product names - "Venafi Cloud" corresponds to CyberArk Certificate Manager SaaS and "Venafi TPP" corresponds to CyberArk Certificate Manager Self-Hosted.

Expand Down Expand Up @@ -283,12 +284,14 @@ You are now ready to issue certificates using the newly provisioned CyberArk
Read the [Requesting Certificates](../usage/certificate.md) document for
more information on how to create Certificate resources.

## Creating an Issuer for Palo Alto Networks Next Generation Trust Services
## Creating an Issuer for Palo Alto Networks Next-Generation Trust Security

The CyberArk `Issuer` supports [Palo Alto Networks Next Generation Trust
Services (NGTS)](https://www.paloaltonetworks.com/sase), a cloud-native
certificate management platform. Authentication uses OAuth 2.0 Client
Credentials, so no API key or username/password is required.
The CyberArk `Issuer` supports [Palo Alto Networks Next-Generation Trust
Security (NGTS)][ngts], a cloud-native certificate management platform.
Authentication uses OAuth 2.0 Client Credentials, so no API key or
username/password is required.
Comment on lines +291 to +292

@wallrj-cyberark wallrj-cyberark Jun 9, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
Authentication uses OAuth 2.0 Client Credentials, so no API key or
username/password is required.
Authentication uses OAuth 2.0 Client Credentials.

I'd drop that last part, personally. It seems unnecessary. Why would the user think that an API key or u/p ARE required?


[ngts]: https://www.paloaltonetworks.com/network-security/next-gen-trust-security

In order to set up an NGTS `Issuer`, you must first create a Kubernetes
`Secret` resource containing your OAuth 2.0 client credentials. The secret
Expand Down Expand Up @@ -317,7 +320,7 @@ or `ClusterIssuer` resource. If you are creating a `ClusterIssuer` resource,
you must change the `kind` field to `ClusterIssuer` and remove the
`metadata.namespace` field.

The `zone` is the name of the Certificate Issuing Template (CIT) in NGTS that will be used to issue certificates. Unlike CyberArk Certificate Manager SaaS, NGTS does not use an Application prefix — the zone is just the CIT name.
The `zone` is the name of the Certificate Issuing Template (CIT) in NGTS that will be used to issue certificates. Unlike CyberArk Certificate Manager SaaS which requires both an Application name and CIT alias in the format `Application\CIT`, NGTS only requires the CIT name.

@wallrj-cyberark wallrj-cyberark Jun 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
The `zone` is the name of the Certificate Issuing Template (CIT) in NGTS that will be used to issue certificates. Unlike CyberArk Certificate Manager SaaS which requires both an Application name and CIT alias in the format `Application\CIT`, NGTS only requires the CIT name.
For NGTS, the `zone` is **only** the name of the Certificate Issuing Template (CIT), that will be used to issue certificates.
> ℹ️ If you are migrating from CyberArk Certificate Manager SaaS or Venafi Cloud, notice that `zone` has a different format. Zone MUST be `CIT`, NOT `Application\CIT`.

I'm not sure if this is clearer. I imagine that most users will skip straight to the NGTS section and may have no knowledge of how CM-SaaS zones are configured....unless they're migrating.


Save the below content after making your amendments to a file named
`issuer.yaml`.
Expand Down