---
title: Zero Page Login Collector node
description: Configure the Zero Page Login Collector node to extract username and password credentials from HTTP headers in an incoming authentication request.
component: platform
version: 7.5
page_id: platform:auth-node-ref:zero-page-login-collector
canonical_url: https://docs.pingidentity.com/platform/7.5/auth-node-ref/zero-page-login-collector.html
llms_txt: https://docs.pingidentity.com/platform/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Nodes & Trees", "Journeys", "Authentication", "Data Store"]
page_aliases: ["auth-node-zero-page-login-collector.adoc"]
section_ids:
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  properties: Properties
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
  node-zero-page-login-example: Example
---

# Zero Page Login Collector node

The Zero Page Login Collector node verifies the presence of specific HTTP username and password headers in the incoming authentication request. If the headers exist, the node uses their corresponding values as the provided username and password.

The Zero Page Login Collector node is commonly used to:

* Connect the `Has Credentials` outcome connector to the input of a [Data Store Decision node](data-store-decision.html).

* Connect the `No Credentials` outcome connector to the input of a [Username Collector node](am-only/username-collector.html) followed by a [Password Collector node](am-only/password-collector.html) (standalone AM) or a [Platform Username node](platform-username.html) followed by a [Platform Password node](platform-password.html) (Ping Identity Platform deployment), and then into the same [Data Store Decision 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 remains in the node state only until the journey reaches the next node that requires user interaction.

## Availability

| Product                               | Available? |
| ------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud       | Yes        |
| PingAM (self-managed)                 | Yes        |
| Ping Identity Platform (self-managed) | Yes        |

## Inputs

* HTTP username header

* HTTP password header

* An allowlist of referrers if `Allow Without Referer` property is disabled. When you set the `Allow Without Referer` property to `false`, the request *must* contain a referrer from the allowlist; otherwise, the journey ends in a failure.

## Dependencies

None.

## Configuration

### 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. An incoming request 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. |

## Outputs

The collected credentials from the headers.

## 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.

## Errors

* If more than one header value exists for username and/or password, the node returns the following error message

  "Expecting only one header value for username and/or password but size is {}."

* If the node can't decode the header values, the node returns the following error message

  "Could not decode username or password header."

## Example

![trees ui example](_images/trees-ui-example.png)Figure 1. AM standalone![zero page login collector node](_images/zero-page-login-collector-node.png)Figure 2. Ping Identity Platform deployment