Upgrading Registry to v3.2.0

CO Group Member Validity Dates

Registry v3.2.0 adds support for valid from and valid through dates for CO Group Memberships. To make full use of these, it will likely be necessary to run the groupvalidity Registry Job Shell.

Organizational Identity Source Plugin resultToGroups() Result Change

For custom Provisioning Plugins that implement resultToGroup(), the return value has changed. See Groupable Attributes for more details.

SalesforceSource Configuration Changes

Registry v3.2.0 changes how server configuration for the Salesforce Source plugin is managed. This change allows multiple plugins to share the same configuration. To update an existing configuration:

1. Add a new Server, via Servers > Add a New Server
   1. Set the server type to OAuth2.
   2. After the configuration has been saved, a Redirect URI will be available via the server configuration page. Keep this handy for the next step.
2. Login to Salesforce and edit the existing configuration for the connected app. Change the Callback URL to the one provided in the OAuth2 server configuration from the previous step.
   1.  It may take several minutes for the new Salesforce configuration to take effect.
3. Return to the OAuth2 Server configuration and complete the configuration.
   1. Server URL: The base URL of your Salesforce instance with /services/oauth2 appended, eg https://test.salesforce.com/services/oauth2
   2. Client ID: The Consumer Key obtained from the Salesforce connected app configuration.
   3. Client Secret: The Consumer Secret obtained from the Salesforce connected app configuration.
   4. Access Token Grant Type: Authorization Code
   5. Scope: (Leave blank)
   6. Click Save.
4. Return to the OAuth2 Server configuration to obtain an OAuth token.
   1. The configuration should indicate that the Access Token is "Not Set", and there should now be a button "Obtain New Token".
   2. Upon clicking that button, you will be taken to the Salesforce login page. Log in as a sufficiently authorized user.
   3. After successful login, you should be returned to the OAuth2 Server configuration page, and the Acess Token should now be "Set".
5. Finally, edit the existing Salesforce Source configuration. Select the server created in step 1 and click Save. You must click Save, even if looks like your server is already selected.

SalesforceSource Additional API Call

As of Registry v3.2.0, during a SalesforceSource retrieve() call, if an Account object is associated with the retrieved object, the Account object will also be retrieved. This consumes an additional API call.