CERT+
Automate certificate lifecycle management including issuance, discovery, renewal, and deployment, across public and private trust CAs. Assess, prioritize, and plan your migration to quantum-safe encryption with the Quantum Trust Hub add-on module.
PKI+
Provision, govern and scale private trust certificates with a Post Quantum ready cloud based Enterprise PKI-as-a-Service.
SIGN+
Secure software, firmware, and containers with a comprehensive enterprise code signing solution.
SSH+
Control SSH access and key rotation at scale with an SSH key lifecycle management solution.
KUBE+
Unify DevOps and Security teams by managing certificates with a Kubernetes-native certificate lifecycle management solution.
DDI+
Manage domain registration, renewal, decommissioning, and other security controls with an end-to-end domain lifecycle management solution.
ADC+
Automate and orchestrate application delivery infrastructure at scale with an ADC lifecycle automation platform.
Platform
Manage policy and automation across all of the products and modules in the AVX ONE platform.
- Platform User Guide
- Platform API Guide
- Reporting User Guide
- Policy Engine
- Automation
  Get started with Automation using workflows for Network Service Orchestration manage inventory, connect tasks and apps, and design workflows to automate routine tasks with AppViewX modules.
AppViewX Setup
Get detailed instructions for setting up AVX ONE in on-premises or SaaS deployments.
Release Artifacts
Review new features, fixes, and security advisories with official AppViewX release documentation.

Troubleshooting

To troubleshoot and resolve the domain/name not resolved error, refer the steps below.

Log in to the mid-server-platform-core container and open the Fortanix log file using the command:
```
vi /tmp/fortanix.log
```
Check the log file for the error thrown by Fortanix. If the error is domain/name not resolved, proceed with the next steps.
Export the proxy URL using the command:
```
export FORTANIX_PROXY=<proxy_url>
```

To manage the keys, run the command:

pkcs11-tool --module <cc_installation>/deps/external_libs/hsm/fortanix/fortanix_pkcs11.so --pin "PIN" -k --label test-key-avx --key-type rsa:2048 --login --login-type user

Navigate to the properties folder using the command
```
cd {CC_INSTALLATION_PATH}/deps/properties
```
Open the hsm file to edit:
```
vi hsm
```

Set the Fortanix proxy and config path in the hsm file by adding the lines below.

export FORTANIX_PROXY=<proxy_url>
export FORTANIX_PKCS11_CONFIG_PATH=/appviewx/dependencies/external_libs/hsm/fortanix/pkcs11.conf
echo "FORTANIX Config Path: $FORTANIX_PKCS11_CONFIG_PATH"

To apply the changes are made in the file, restart the avx-mid-server-platform pod uging the commands below.
```
kubectl get pods -n <namespace>
```
```
kubectl delete pods -n <namespace> <PodName>
```

AppViewX