---
title: Aquera Provisioner
description: The Aquera Provisioner allows PingFederate to integrate with any application supported by Aquera for user provisioning and single sign-on (SSO).
component: aquera
page_id: aquera::pf_aquera_connector
canonical_url: https://docs.pingidentity.com/integrations/aquera/pf_aquera_connector.html
revdate: June 27, 2024
section_ids:
  features: Features
  intended-audience: Intended audience
  system-requirements: System requirements
---

# Aquera Provisioner

The Aquera Provisioner allows PingFederate to integrate with any application supported by Aquera for user provisioning and single sign-on (SSO).

## Features

* Manages users in the target service based on changes in an external data store that is attached to PingFederate.

  * Creates, updates, disables, and deletes users.

  * Allows you to enable the create, update, disable, and delete capabilities independently.

  * Allows you to choose whether to disable or delete users when deprovisioning.

  * Allows you to provision disabled users.

* Manages groups in the target service based on changes in an external data store that is attached to PingFederate.

  * Creates, updates, and deletes groups.

  * Updates group memberships.

* Enables browser-based SSO initiated by the service provider (SP) or identity provider (IdP).

The Aquera Provisioner implements the official SCIM specifications provided from [simplecloud.info](http://www.simplecloud.info/). The following table provides a brief summary.

| Feature                        | Outbound provisioning                                                                                                           |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| SCIM specification             | Step 2.0                                                                                                                        |
| Data format                    | JSON                                                                                                                            |
| User and group CRUD operations | Yes                                                                                                                             |
| Custom schema support          | Yes. The connector retrieves the target service schema from Aquera.                                                             |
| Filtering support              | Users: YesGroups: Yes, if the target service supports it. Otherwise, the connector attempts to get all groups and find a match. |
| PATCH                          | Users: NoGroups: Yes                                                                                                            |
| Authentication method          | Basic authentication and bearer token authentication                                                                            |
| Source data stores             | Active Directory and other LDAPv3-compliant directory servers                                                                   |

Attribute support varies by target service. The Aquera Provisioner dynamically gets attributes from Aquera for each target service.

## Intended audience

This document is intended for PingFederate administrators.

Learn more about the setup process from the following resources:

* PingFederate documentation:

  * [SP connection management](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_sp_connect_management.html)

  * [Identity provider SSO configuration](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_ident_provid_sso_config.html)

  * [Managing digital signing certificates and decryption keys](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_certmanagementtasklet_dsigsigningcert_certmanagementstate.html)

  * [Datastores](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_datastores.html)

  * [Configuring outbound provisioning](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_spconnectionconfigtasklet_saasprovisioningstate.html)

  * [Configuring outbound provisioning settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_protocolsettingstasklet_saasglobalprovisioningsettingsstate.html)

* Aquera documentation:

  * [Aquera User Guide](https://support.aquera.com/hc/en-us/articles/360056052093-Aquera-User-Guide)

  * [Connectors](https://support.aquera.com/hc/en-us/categories/115000284613-Connectors) documentation for the target service

## System requirements

* PingFederate 9.0 or later.

* To allow PingFederate to make outbound connections, you might need to allow the following Aquera endpoint (use your tenant ID):

  * http\://api.aquera.com/Tenants/:*tenantid*