Evernote Provisioner

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 an SP connection and may be added to an existing SP connection.

Single sign-on is required for SCIM provisioning with Evernote. SCIM is only available in Evernote Business accounts created on or after September 15, 2017. For more information, see How to determine when an Evernote Business account was created.

Steps

  1. In the PingFederate administrator console, configure the data store that PingFederate will use as the source of user data.

    For instructions, see Datastores 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 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.
    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. For more information on obtaining the bearer token, see Configure Evernote for provisioning.

    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 Business 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.

    For more information, see the following sections under Outbound provisioning for IdPs in the PingFederate documentation: