The following is the change history for the Salesforce Provisioner.
Salesforce Connector 7.0.1 – April 2020
- Fixed an issue that caused the connection check to return a success when the wrong subdomain was entered.
Salesforce Connector 7.0 – September 2019
- Added support for provisioning to Salesforce Community Cloud (customer, partner, and custom communities).
- Added the ability to create connections to custom Salesforce domains.
- Added support for version 46.0 of the Salesforce REST API.
- Added configuring options to manage permission sets by merging or overwriting.
- Added support for additional salesforce attributes.
- Added the ability to create multiple Salesforce connections in one PingFederate instance.
- Added default attribute mappings for channels that use PingDirectory and Oracle Directory Server data stores.
- Improved error handling and reporting for cases where users in the target application do not have an ID.
- Improved error handling and reporting for cases where groups are updated or deleted but do not exist in the target application.
- Fixed an issue that prevented users with certain special characters from being provisioned to Salesforce.
- Fixed an issue that caused a user to be updated in Salesforce when the user was being disabled and the Update Users option was turned off.
Salesforce Connector 6.1 – July 2017
- Added support for disabling user without updating any user attributes
- Added configuration control of provisioning disabled users
- Added custom attribute support
- Removed non-mappable attributes from attribute mapping screen
Salesforce Connector 6.0 – October 2016
- Added Support for additional User attributes
- Added Support for Group Provisioning
- Added Support for adding Users to Groups
- Added configuration options for CRUD capabilities
- Improved exception handling and reporting
- Added support for Salesforce REST v37.0 API
- Added support for the OAuth Authentication with the OAuth Configuration Service (OCS)
- Removed support for Delegated Authentication in favor of SAML (deprecated)
- Removed support for Outbound Provisioning to Partner and Customer Portals (deprecated)
Salesforce Connector 5.1.1 – November 2015
- Added support for Salesforce API endpoint change (January 1, 2016).
Salesforce Connector 5.1 – August 2015
- Added support for SSO to Veeva iRep mobile clients via delegated authentication with Salesforce
- Fixed quick-connection UI performance issues
- Added support for the ability to freeze user accounts instead of deactivating them via the provisioner
- Added support for overriding the provisioning target environment endpoint
- Enhanced support for SP-Initiated SSO via deep linking and SP-initiated SLO by adding a Salesforce Login URL & Single Logout Landing Page field
Salesforce Connector 5.0 – October 2014
- Added ability to have one LDAP user mapped to two different Salesforce administrator accounts
- Salesforce API updated from version 20 to version 31
- Added Permission Set attribute to SP Connection, which enables mapping of permission sets in Salesforce to an LDAP field
- Added support for proxy authentication
Salesforce Connector 4.1 - June 2011
- Added support for Salesforce Chatter and Chatter Free user provisioning
Salesforce Connector 4.0.1 - November 2010
- Corrected compatibility issue with PingFederate 6.4
Salesforce Connector 4.0 - November 2010
- Added quick-connection SSO template and enabled SaaS Provisioning to the Salesforce Customer Portal
- Added quick-connection SSO template and enabled SaaS Provisioning to the Salesforce Partner Portal
- Added quick-connection SSO template to support Salesforce CRM SAML capabilities including metadata export from Salesforce and import into PingFederate, plus optional SaaS Provisioning
Salesforce Connector 3.3 - May 2009
- Added support for Salesforce “Connect for Microsoft Outlook” version 3.2.513
- Added an option to remove the email domain from the Salesforce Username for OpenToken authentication by the Authentication Web Service
Salesforce Connector 3.2 - January 2009
- Added a quick-connection plug-in component for automated SSO configuration and SaaS Provisioning support for use with PingFederate 5.3
- dded support for Mutual Transport Layer Security (TLS) between Salesforce and the PingFederate Authentication Service
- Added an option to remove the email domain from the Salesforce User Name for authentication to a LDAP directory
- Added support for delegated authentication to Salesforce via Salesforce Mobile Clients
- Combined the former Salesforce User Guide into the Salesforce Quick Connection Guide
Salesforce Connector 3.1 - September 2008
- Support for URL Deep Linking
- Obfuscated LDAP password in the configuration file
- Enabled Single Logout from Salesforce
- Included Salesforce Quick Connection Guide for PingFederate 5.2
- Changed the product name to Salesforce Connector
Salesforce.com Integration Kit 3.0 - May 2008
- Support for Salesforce “Connect for Microsoft Outlook” plug-in through a new Desktop Proxy Service that allows the use of corporate credentials for access to Salesforce
- Uses OpenToken for the encrypted token format rather than PFTOKEN
Salesforce.com Integration Kit 2.0 - July 2007
- Provisioning (new user creation on the Salesforce side)
- PingFederate v4 administrative console Salesforce configuration for optional provisioning and direct Salesforce login
- Salesforce Web Service user-validation changes
- Certification on Salesforce AppExchange
Salesforce.com Integration Kit 1.1 - November 2006
Use of the PingFederate Standard Adapter, eliminating the Salesforce.com Adapter that was specific to this Integration Kit
Salesforce.com Integration Kit 1.0 - June 2006