Support for ForgeOps

This appendix contains information about support options for ForgeOps deployments and the Ping Identity Platform.

ForgeOps support

Ping Identity ForgeOps team has developed artifacts in the forgeops and forgeops-extras Git repositories for deploying the Ping Identity Platform in the cloud. The companion ForgeOps documentation provides examples to help you get started.

These artifacts and documentation are provided on an "as is" basis. Ping Identity does not guarantee the individual success developers may have in implementing the code on their development platforms or in production configurations.

Licensing

Ping Identity only offers its software or services to legal entities that have entered into a binding license agreement with Ping Identity. When you install Docker images provided by ForgeOps, you agree either that: 1) you are an authorized user of a Ping Identity Platform customer that has entered into a license agreement with Ping Identity governing your use of the Ping Identity software; or 2) your use of the Ping Identity Platform software is subject to the Ping Identity Subscription Agreements.

Support

Ping Identity provides support for the following resources:

Artifacts in the forgeops Git repository:
- Files used to build Docker images for the Ping Identity Platform:
  - Dockerfiles
  - Scripts and configuration files incorporated into the Docker images provided by ForgeOps
  - Canonical configuration profiles for the platform
- Helm charts
- Kustomize bases and overlays
ForgeOps Documentation

For more information about support for specific directories and files in the forgeops repository, refer to the forgeops repository reference.

Ping Identity provides support for the Ping Identity Platform. For supported components, containers, and Java versions, refer to the following:

Support limitations

Ping Identity provides no support for the following:

Artifacts in the forgeops-extras repository. For more information about support for specific directories and files in the forgeops-extras repository, refer to the forgeops-extras repository reference.
Artifacts other than Dockerfiles, Helm charts, Kustomize bases, and Kustomize overlays in the forgeops Git repository. Examples include scripts, example configurations, and so forth.
Infrastructure outside Ping Identity. Examples include Docker, Kubernetes, Google Cloud Platform, Amazon Web Services, Microsoft Azure, and so forth.
Software outside Ping Identity. Examples include Java, Apache Tomcat, NGINX, Apache HTTP Server, Certificate Manager, Prometheus, and so forth.
Deployments that deviate from the published ForgeOps architecture. Deployments that do not include the following architectural features are not supported:
- PingAM (AM) and PingIDM (IDM) are integrated and deployed together in a Kubernetes cluster.
- IDM login is integrated with AM.
- AM uses PingDS (DS) as its data repository.
- IDM uses DS as its repository.
Ping Identity publishes reference Docker images for testing and development, but these images should not be used in production. For production deployments, it is recommended that customers build and run containers using a supported operating system and all required software dependencies. Additionally, to help ensure interoperability across container images and the ForgeOps tools, Docker images must be built using the Dockerfile templates as described here.

Third-party Kubernetes services

The ForgeOps reference tools are provided for use with Google Kubernetes Engine, Amazon Elastic Kubernetes Service, and Microsoft Azure Kubernetes Service. (ForgeOps is supported on IBM RedHat OpenShift but the reference tools for IBM RedHat OpenShift are not provided.)

Ping Identity supports running the platform on Kubernetes. Ping Identity does not support Kubernetes itself. You must have a support contract in place with your Kubernetes vendor to resolve infrastructure issues. To avoid any misunderstandings, it must be clear that Ping Identity cannot troubleshoot underlying Kubernetes issues.

Modifications to ForgeOps deployment assets may be required in order to adapt the platform to your Kubernetes implementation. For example, ingress routes, storage classes, NAT gateways, etc., might need to be modified. Making the modifications requires competency in Kubernetes, and familiarity with your chosen distribution.

Documentation access

Ping Identity publishes comprehensive documentation online:

The Knowledge Base offers a large and increasing number of up-to-date, practical articles that help you deploy and manage Ping Identity Platform software.

While many articles are visible to community members, Ping Identity customers have access to much more, including advanced information for customers using Ping Identity Platform software in a mission-critical capacity.
The developer documentation, such as this site, aims to be technically accurate with respect to the sample that is documented. It is visible to everyone.

Problem reports and information requests

If you are a named customer Support Contact, contact Ping Identity using the Customer Support Portal to request information, or report a problem with Dockerfiles, Helm charts, Kustomize bases, or Kustomize overlays in the forgeops repository.

When requesting help with a problem, include the following information:

Description of the problem, including when the problem occurs and its impact on your operation.
Steps to reproduce the problem.

If the problem occurs on a Kubernetes system other than Minikube, GKE, EKS, or AKS, we might ask you to reproduce the problem on one of those.
HTML output from the debug-logs command. For more information, refer to Kubernetes logs and other diagnostics.

Suggestions for fixes and enhancements to artifacts

ForgeOps greatly appreciates suggestions for fixes and enhancements to ForgeOps-provided artifacts in the forgeops and forgeops-extras repositories.

If you would like to report a problem with or make an enhancement request for an artifact in either repository, create a GitHub issue on the repository.

Contact information

Ping Identity provides support services, professional services, training through Ping Identity training, and partner services to assist you in setting up and maintaining your deployments. For a general overview of these services, refer to https://www.pingidentity.com/en/platform.html.

Ping Identity has staff members around the globe who support our international customers and partners. Learn more about Ping Identity’s support offering, including support plans and service-level agreements (SLAs) at the Ping Identity Platform support page.