Sometimes changes to your integration are necessary - it might be changing to MemberSuites Portal 5 for SSO, or upgrading your instance of Personify. Whatever your reason or need to ensure the best experience - begin your process with a case with our support team.

While we understand that sometimes changes may need to be quick - in general, we ask for 2 - 3 weeks' notice so that we can confirm the scope of the change, and adequate tests to ensure that there is no disruption to your membership.

An Integration change is outlined as an update, upgrade or process change with your current AMS provider - if you are looking to switch your AMS solution entirely head over to Steps to a Successful CRM/AMS Migration.

Updating or Changing an SSO Provider

Higher Logic Thrive Community (Thrive Community) supports the following methods for SSO: OpenID Connect, OAuth 2.0, SAML 2.0 and, some AMS platforms provide out-of-the-box solutions.

Pre-Change Steps

Depending on what solution you are pursuing - there is additional documentation that may be required.  Our Support team will be supplying the worksheet we need to proceed with the change. 

1. Notify Higher Logic (preferably two to three weeks in advance) of the upcoming change
2. Supply details of the change (ex. we're switching to SAML) 
3. Supply the test credentials (username and password to us via your support case)
4. Let us know the date of the change 

Testing Steps

1. We'll confirm if any changes need to be made the day of (e.g., changing the sign on and sign off URL).
2. Higher Logic will then test that change in either a temporary community or via API calls.  We'll confirm if the change is compatible with your services and whether the test credentials return a successful response.

Day of Change Steps

1. Higher Logic will update the configuration parameters confirmed during the testing phase.
2. Higher Logic will then test that the change has been applied and if the test credentials return a successful response.
3. We'll ask that your team tests as well to ensure that there is no disruption.

Upgrading your AMS Platform 

If you're using a database-driven AMS (ex. Personify) we'll need to collect information related to the change from you. 

Pre-Change Steps

1. Notify Higher Logic (preferably two to three weeks in advance) of the upcoming change.
2. Supply details of the change (ex. we're upgrading to version 7.7).
   1. We may need additional information from you based on the integration - our team will supply what the current credentials of your integration are and whether they need to be changed. 
3. Supply test credentials (username and password to us via your support case) if you are not leveraging SSO - this step can be skipped.
4. Let us know the date of the change. 

Testing Steps

1. We'll confirm if any changes need to be made the day of the change. 
2. If you have a test server - we can confirm that the integration is operational based on a set of API calls to your service.

Day of Change Steps

1. Higher Logic will update the configuration parameters confirmed during the testing phase.
2. Higher Logic will then test that the change has been applied and if the test credentials return a successful response.
3. We'll ask that your team tests as well to ensure that there is no disruption.