---
title: Zero Page Login Collector node
description: 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.
component: auth-node-ref
version: latest
page_id: auth-node-ref::zero-page-login-collector
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/zero-page-login-collector.html
keywords: ["Nodes & Trees", "Journeys", "Authentication", "Data Store"]
page_aliases: ["auth-node-zero-page-login-collector.adoc"]
superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/zero-page-login-collector.html
section_ids:
  node-zero-page-login-example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
---

# 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 username and password collector nodes.

* Then connect into the same [Data Store Decision node](data-store-decision.html).

The password collected by this node remains in the node state only until the journey reaches the next node that requires user interaction.

## Example

![zero page login collector node](_images/zero-page-login-collector-node.png)

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

This node has no dependencies.

## Configuration

| 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

  The specified headers are available in the request.

* No Credentials

  The specified headers aren't available in the request.

## Errors

The node can log the following errors:

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

  More than one header value exists for the username and/or password.

* `Could not decode username or password header.`

  The node can't decode the header values.