Evernote Provisioner

Upgrade an existing connector

Steps

  1. Before stopping the PingFederate server to upgrade the Evernote Connector, access the Attribute Mapping screen for existing channel configurations and note the current configuration.

    The upgrade process removes existing mappings and defaults on the Attribute Mapping screen. These must be configured again before activating the channel configuration.

  2. Disable the existing SP connection where the Evernote Connector is configured.

  3. Delete the existing Evernote Connector SP connection and save.

  4. Stop the PingFederate server if it is running.

  5. Unzip the new Evernote Connector distribution .zip archive into a holding directory.

  6. Remove any older versions of pf-evernote-quickconnection-[version].jar from:

    <pf_install>/pingfederate/server/default/deploy

  7. Remove the following files from the same directory if they are present:

    • evernote-business-provisioning-api-1.28.jar

    • pf-evernote-oauth-helper.war

  8. From the dist directory of the new version of the connector, copy the file:

    [.filepath]``pf-evernote-quickconnection-2.0.jar``

    into the directory:

    [.filepath]`` [.varname]__<pf_install>__/pingfederate/server/default/deploy``

  9. Start the PingFederate server.

  10. Create a new SP connection, using Evernote Connector as the connection template.

  11. Follow instructions in Configure PingFederate for SSO and Configure PingFederate for provisioning in order to configure metadata.

  12. Access the Attribute Mapping screen for existing channel configurations and click Refresh Fields.

  13. Ensure all new required fields (if any), are mapped appropriately or have a default value.

  14. When you have completed the attribute configuration, click Done, Done, and Save.

  15. Activate the SP connection to resume outbound provisioning.