---
title: Zero Page Login Collector node
description: Checks whether selected headers are provided in the incoming authentication request, and if so, uses their values as the provided username and password.
component: auth-node-ref
version: 7.3
page_id: auth-node-ref::auth-node-zero-page-login-collector
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/zero-page-login-collector.html
llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
section_ids:
  outcomes: Outcomes
  properties: Properties
  node-zero-page-login-example: Example
---

# Zero Page Login Collector node

Checks whether selected headers are provided in the incoming authentication request, and if so, uses their values as the provided username and password.

A common use for the Zero Page Login Collector authentication node is to connect the `Has Credentials` outcome connector to the input of a [Data Store Decision node](auth-node-data-store-decision.html), and the `No Credentials` outcome connector to the input of:

* A [Username Collector node](am-only/auth-node-username-collector.html) followed by a [Password Collector node](am-only/auth-node-password-collector.html) (Access Management deployments)

* A [Platform Username node](auth-node-platform-username.html) followed by a [Platform Password node](auth-node-platform-password.html) (Ping Identity Platform deployments)

Those are then connected into the same same [Data Store Decision node](auth-node-data-store-decision.html).

Find an example of this layout in the default `Example` authentication tree provided in AM.

The password collected by this node is transient, persisting only until the next node requiring user interaction.

## Outcomes

* `Has Credentials`

* `No Credentials`

Evaluation continues along the `Has Credentials` outcome path if the specified headers are available in the request, or the `No Credentials` path if the specified headers are not present.

## Properties

| Property              | Usage                                                                                                                                                                                                                                                                                                                                                              |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Username Header name  | Enter the name of the header that contains the username value.Default: `X-OpenAM-Username`                                                                                                                                                                                                                                                                         |
| Password Header name  | Enter the name of the header that contains the password value.Default: `X-OpenAM-Password`                                                                                                                                                                                                                                                                         |
| Allow without referer | If enabled, the node accepts incoming requests that do not contain a `Referer` HTTP header. If a `Referer` HTTP header is present, the value is not checked.If disabled, a `Referer` HTTP header must be present in the incoming request, and the value must appear in the Referer allowlist property.Default: `Enabled`                                           |
| Referer Whitelist     | Specify a list of URLs allowed in the `Referer` HTTP header of incoming requests. Incoming requests containing a `Referer` HTTP header value not specified in the allowlist causes evaluation to continue along the `No Credentials` outcome path.

You must disable the Allow Without Referer property for the referer allowlist property to take effect. |

## Example

![The Example authentication tree, showing Zero Page Login node use.](_images/trees-ui-example.png)