---
title: Adding virtual issuers for OpenID Connect
description: You can define one or more virtual issuers for OpenID Connect, with or without a relative path. When minting an ID token, PingFederate populates the issuer claim according to the virtual issuer setting and the authorization request.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:pf_adding_virtual_issuers_openid_connect
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_adding_virtual_issuers_openid_connect.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: July 10, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Adding virtual issuers for OpenID Connect

You can define one or more virtual issuers for OpenID Connect, with or without a relative path. When minting an ID token, PingFederate populates the issuer claim according to the virtual issuer setting and the authorization request.

## About this task

To add a virtual issuer to PingFederate, perform the following procedure. If you have multiple virtual issuers, ensure the combination of host and path values are unique.

|   |                                                                                                                                                                                                                           |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | After you define virtual issuers, you can map them to sets of ID token signing keys. For more information, see [Mapping ID token signing keys to virtual issuers](pf_mapping_id_token_signing_keys_virtual_issuers.html). |

## Steps

1. Go to **System > OAuth Settings > Virtual Issuers**.

2. Click **Add Virtual Issuer**.

3. Enter a unique issuer **Name**.

4. Enter the **Host**.

5. Optional: Enter the relative **Path**, which must start with the value of the `pf.runtime.context.path` property in the `run.properties` file.

6. Click **Save**.