<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Accessing the PPC CLI on</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/access_cli/</link><description>Recent content in Accessing the PPC CLI on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/access_cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Prerequisites</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/access_cli/prereqs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/access_cli/prereqs/</guid><description>&lt;p>To access the PPC CLI, ensure that the following prerequisites are met.&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>SSH Keys&lt;/strong>:
The SSH private key that corresponds to the public key configured in the &lt;code>pty-cli&lt;/code> pod is required.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Network Access&lt;/strong>:
Ensure to have network connectivity to the cluster.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Resolve FQDN&lt;/strong>:
Use Route 53 configuration on AWS to resolve the PPC FQDN specified during the installation to the internal load balancer.
For more information, refer to &lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/access_ui/prereq/">Prerequisites&lt;/a>.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;h3 id="for-linuxmacos-users">For Linux/macOS Users&lt;/h3>
&lt;p>The private key to access the CLI pod will be in the &lt;code>/deployment/keys&lt;/code> directory. The key file is &lt;code>authorized_keys&lt;/code>.&lt;/p></description></item><item><title>Accessing the PPC CLI</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/access_cli/access/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/access_cli/access/</guid><description>&lt;p>Once connected, the Protegrity CLI welcome banner displays. Enter the following parameters when prompted:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Username&lt;/strong>: Application username&lt;/li>
&lt;li>&lt;strong>Password&lt;/strong>: Application password&lt;/li>
&lt;/ul>
&lt;p>For more information about the default credentials, refer to the &lt;em>Release Notes&lt;/em>.&lt;/p>
&lt;p>The CLI supports two main command categories:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;code>pim&lt;/code>&lt;/strong>: Policy Information Management commands for data protection policies&lt;/li>
&lt;li>&lt;strong>&lt;code>admin&lt;/code>&lt;/strong>: User, Role, Permission, and Group management commands&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&lt;strong>Note&lt;/strong>: Ensure that at least one additional backup administrator user is configured with the same administrative privileges as the primary admin user. &lt;br>If the primary admin account is locked or its credentials are lost, restoring the system from a backup may be the only recovery option.&lt;/p></description></item></channel></rss>