Sometimes, changes to your integration environment are necessary. For example, you might be changing to MemberSuites Portal 5 for Single Sign-On (SSO), or upgrading your instance of Personify. Whatever your reason, create a case with our Support team.

NOTE: Are you planning an SSO implementation with Higher Logic? If so, your implementation project may require a one-time fee for configuration and testing. Reach out to us to learn more.

While we understand that sometimes changes may have to happen quickly, typically, we prefer 2 – 3 weeks' notice so that we can confirm the scope of the change and adequately test to ensure that there is no disruption to your membership.

An integration change is outlined as an update, upgrade, or process change with your AMS or CRM provider. However, if your plan is to switch to a different AMS or CRM solution, see Steps to a Successful CRM/AMS Migration.

IMPORTANT: iMIS customers who are upgrading to iMIS cloud (version 20.3 or higher) and Protech customers who are upgrading to Protech UX365 must run an AMS migration project. For help with this, create a case with our Support team 10 weeks before your expected migration date.

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

Some AMS/CRM providers provide out-of-the-box solutions.

Pre-change steps

Depending on what solution you are pursuing, additional documentation 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 change
2. Provide details of the change (e.g., we're switching to SAML)
3. Provide the test credentials (username and password) to us via your support case
4. Provide the date of the change

Testing steps

1. Higher Logic will confirm whether any changes need to be made the day of the change (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.
3. Higher Logic will confirm whether 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 whether the test credentials return a successful response.
3. Higher Logic asks 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 (such as Personify), Higher Logic will 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. Provide details of the change (e.g., we're upgrading to version 7.7)
   1. We may need additional information from you based on the integration; our team will indicate what your current integration credentials are and whether they need to be changed.
3. Provide test credentials (username and password) to us via your support case (if you are not leveraging SSO, skip this step)
4. Provide the date of the change

Testing steps

1. Higher Logic will confirm if any changes need to be made the day of the change.
2. If you have a test server, Higher Logic 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. Higher Logic asks that your team tests as well to ensure that there is no disruption.