---
title: Defining encoding for binary attributes
description: Use the LDAP Binary Attribute Encoding Types window to specify an encoding type to apply during fulfillment.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:pf_defining_encoding_binary_attributes
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_defining_encoding_binary_attributes.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
  example: Example
---

# Defining encoding for binary attributes

Use the **LDAP Binary Attribute Encoding Types** window to specify an encoding type to apply during fulfillment.

## About this task

The **LDAP Binary Attribute Encoding Types** window appears when at least one attribute is configured as such in the datastore. Because you cannot use binary attribute data in an assertion to the service provider (SP), you must specify the encoding type that you want to apply during fulfillment. The available choices are **Base64**, **Hex**, and **SID**.

|   |                                                                                                                         |
| - | ----------------------------------------------------------------------------------------------------------------------- |
|   | Defining encoding for binary attributes is only applicable to identity provider (IdP) and IdP-to-SP bridging use cases. |

## Steps

1. To set an encoding type, select a value from the **Attribute Encoding Type** list.

   Repeat this step for each binary attribute.

## Example

Examples

Microsoft Office 365 relies on an immutable Active Directory binary attribute associated with user accounts (`objectGUID`), and requires this binary data to be Base64-encoded to correlate provisioned federated user data to Active Directory accounts. Select **Base64** from the **Attribute Encoding Type** list.

Claims-based authentication with Microsoft Outlook Web App and Exchange admin center (EAC) requires `tokenGroups` (another binary attribute in Active Directory) to be SID-encoded. Select **SID** from the **Attribute Encoding Type** list.