---
title: Installing and uninstalling PingFederate
description: PingFederate operates as a standalone server based on Java EE application server technology. This section shows you how to properly install PingFederate.
component: pingfederate
version: 13.1
page_id: pingfederate:installing_and_uninstalling_pingfederate:pf_installing_uninstalling_pf
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/installing_and_uninstalling_pingfederate/pf_installing_uninstalling_pf.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: September 3, 2025
section_ids:
  deployment-options: Deployment options
  related-links: Related links
---

# Installing and uninstalling PingFederate

PingFederate operates as a standalone server based on Java EE application server technology. This section shows you how to properly install PingFederate.

A new installation involves:

* Determining the deployment architecture

* Reviewing [system](pf_system_requirements.html) and [port](pf_port_requirement.html) requirements

* [Installing a Java runtime environment](pf_install_java.html)

* [Installing PingFederate](pf_installing_pf.html)

* Completing the Initial Setup wizard

|   |                                                                                                                                                                                                                                                                                                          |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | To avoid issues with browsers honoring [Private Network Access](https://wicg.github.io/private-network-access/) security practices, you should make PingFederate accessible on a public network address if you intend to use it with applications or partners that would be considered public resources. |

## Deployment options

Depending on your needs and infrastructure capabilities, you can choose a standalone or proxy configuration. For information about configuring proxy settings, see [Configuring incoming proxy settings](../administrators_reference_guide/help_systemoptionstasklet_systemoptionsstate.html) and [Configuring forward proxy server settings](../administrators_reference_guide/pf_configure_forward_proxy_server_settings.html).

The following diagram illustrates a standalone PingFederate deployment in a DMZ.

![A diagram showing installation in a DMZ](_images/pf_standalone_config_dmz.png)

In this configuration, the users access PingFederate through a web application server, an enterprise identity management (EIM) system, or both. PingFederate then retrieves information from a datastore to use in processing the transaction.

You can also deploy PingFederate with a proxy server. The following diagram depicts a proxy-server configuration in which users and web browsers access the proxy. The proxy then communicates with PingFederate to request single sign-on (SSO) *(tooltip: \<div class="paragraph">
\<p>The process of authenticating an identity (signing on) at one website (usually with a user ID and password) and then accessing resources secured by other domains without reauthenticating.\</p>
\</div>)*.

![A diagram showing a proxy-server configuration in which users and web browsers access the proxy](_images/pf_proxy_server_config.png)

## Related links

* [Upgrading PingFederate](../upgrading_pingfederate/pf_upgrade_pf.html)

* [Uninstalling PingFederate](pf_uninstall_pf.html)