--- title: Configure PingFederate for provisioning description: To configure a connection for outbound provisioning to Evernote, follow the instructions in this section. Outbound provisioning details are managed within a service provider (SP) connection and can be added to an existing SP connection. component: evernote page_id: evernote:setup:pf_evernote_connector_configure_pf_for_provisioning canonical_url: https://docs.pingidentity.com/integrations/evernote/setup/pf_evernote_connector_configure_pf_for_provisioning.html revdate: June 11, 2024 section_ids: about-this-task: About this task steps: Steps --- # Configure PingFederate for provisioning ## About this task To configure a connection for outbound provisioning to Evernote, follow the instructions in this section. Outbound provisioning details are managed within a service provider (SP) connection and can be added to an existing SP connection. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | Single sign-on (SSO) is required for SCIM provisioning with Evernote. SCIM is available only in Evernote Teams accounts created on or after September 15, 2017. Learn more in [How to determine when an Evernote Teams account was created](https://help.evernote.com/hc/articles/115011455527) in the Evernote documentation. | ## Steps 1. In the PingFederate administrative console, configure the datastore that PingFederate will use as the source of user data. Learn more in [Datastores](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_managedatasourcestasklet_managedatasourcesstate.html) in the PingFederate documentation. * When targeting users and groups for provisioning, exclude the user account that you will use to administer users in your connection to Evernote. This prevents the PingFederate provisioning engine from interfering with the account that provisions users and groups. 2. Select the existing SP connection created in [Configure PingFederate for SSO](pf_evernote_connector_configure_pf_for_sso.html) from the **Identity Provider > SP Connections > Manage All** menu. 3. On the **Activation & Summary** screen, go to **Connection Type** and select the **Outbound Provisioning** and **Browser SSO Profiles** checkboxes. 4. On the **Outbound Provisioning** screen, click **Configure Provisioning**. 5. On the **Target** screen, enter the values for each field as required by the Evernote Connector. ![A screen capture of the Target screen.](_images/kqb1563995312793.png) **Target screen options** | Field Name | Description | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Base URL** | The base URL for Evernote.- https\://m1.svc.evernote.com/scim/v2/ | | **Bearer Token** | The bearer token used by the connector to make authenticated API calls to Evernote. Learn more about obtaining the bearer token in [Configure Evernote for provisioning](pf_evernote_connector_configure_evernote_for_provisioning.html). | | **Provisioning Options** | | | **User Create** | **True** (default): Users will be created in Evernote. Due to Evernote API limitations, new users cannot be created with the same username as a previously deactivated user.**False**: Users will not be created in Evernote. The provisioner.log will display a warning within the create user workflow that the user was not created in Evernote. | | **User Update** | **True** (default): Users will be updated in Evernote.**False**: Users will not be updated in Evernote. The provisioner.log will display a warning within the update user workflow that the user was not updated in Evernote. | | **User Disable** | **True** (default): Users will be disabled in Evernote. Due to Evernote API limitations, once a user is deactivated, they cannot be reactivated with the provisioner. A deactivated user can only be reactivated in the Evernote Teams Admin Console.**False**: Users will not be disabled in Evernote. The provisioner.log will display a warning within the user workflow that the user was not disabled in Evernote. | 6. Click **Next** to continue the provisioning configuration. Learn more in the following sections under [Outbound provisioning for IdPs](https://docs.pingidentity.com/pingfederate/latest/introduction_to_pingfederate/pf_outboun_provis_for_idp.html) in the PingFederate documentation: * [Managing channels](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saasmanagementtasklet_saasmanagementstate.html) * [Specifying channel information](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saasgeneralinfostate.html) * [Identifying the source datastore](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saassourceselectionstate.html) * [Modifying source settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saassourcesettingsstate.html) * [Specifying a source location](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saassourcelocationstate.html) * [Mapping attributes](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saasattrmappingmgmtstate.html) * [Reviewing channel settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saasactivationstate.html) | | | | - | --------------------------------------------------------------------------------------------------------------- | | | Credentials will be verified when the channel and SP connection is set to Active and provisioning is initiated. | | | | | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | If you are not ready to complete the provisioning configuration, you can click **Save** and return to the configuration page later. To return to the configuration page, select the connection from **Identity Provider > SP Connections > Manage All**. |