---
title: Write Federation Information node
description: Configure the Write Federation Information node to create a persistent SAML 2.0 account link between a remote identity provider and a local service provider account.
component: auth-node-ref
version: 8
page_id: auth-node-ref::write-federation-information
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/write-federation-information.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
revdate: 2026-09-01T13:00:59Z
keywords: ["Nodes & Trees", "Journeys", "Authentication", "Federation", "SAML 2.0", "Single Sign-on (SSO)"]
page_aliases: ["auth-node-write-federation-information.adoc"]
superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/write-federation-information.html
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  callbacks: Callbacks
  outcomes: Outcomes
  errors: Errors
---

# Write Federation Information node

The Write Federation Information node creates a persistent link between a remote IdP account and a local account in the SP, if none exists yet. If a transient link exists, it's persisted. Existing account links with different IdPs aren't lost.

Use this node with the [SAML2 Authentication node](saml2.html), and ensure that the NameID Format is `persistent`.

## Example

You can find examples that show this node in a SAML 2.0 authentication journey in [SSO in integrated mode](https://docs.pingidentity.com/pingam/8/am-saml2/saml2-integrated-mode.html).

## Availability

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

## Inputs

The node requires the `userInfo` shared state property from a preceding SAML2 Authentication node. The property must contain the configured persistent NameID attribute.

## Dependencies

* Use the node in a SAML 2.0 authentication journey.

* Configure the SAML 2.0 federation to use the `persistent` NameID Format.

## Configuration

This node has no configurable properties.

## Outputs

The node persists the link between the remote IdP account identified by the NameID and the local SP account.

## Callbacks

This node doesn't send any callbacks.

## Outcomes

Single outcome path.

## Errors

The node can log the following errors:

* `No user information has been found in the shared state.`

  A preceding node didn't set the `userInfo` shared state property.

* `<NameID information attribute> is not defined in shared state.`

  The `userInfo` property doesn't contain the NameID information attribute.

* `Unable to link accounts`

  The node couldn't persist the account link. Check the SAML 2.0 configuration and the local user identity.