SOTI Identity Configuration Post SOTI MobiControl Migration

After migrating SOTI MobiControl from one server to another server, the instance may receive a new server name, resulting in a new Fully Qualified Domain Name (FQDN). However, this change will not be automatically reflected in SOTI Identity. The FQDN needs to be manually updated for SOTI Identity to establish proper communication with it.

In this article, it is assumed that a SOTI MobiControl server migration took place and was successful. 

The next step is to configure SOTI Identity to access the proper FQDN. In this article,  https://A000000A.mobicontrol.cloud is an example FQDN for the new server.

1. Login to SOTI Identity.

2. Select the menu > Applications.

3. Select the current SOTI MobiControl app in use in SOTI Identity. In this example, it is MOBICONTROL.

4. Change the application name by adding the FQDN. Example: MOBICONTROL - YourFQDN.

5. Update the FQDN for the values mentioned below. Select Update to save your changes.

SAML Audience: https://A000000A.mobicontrol.cloud/mobicontrol

SAML Consumer URL: https://A000000A.mobicontrol.cloud/mobicontrol/sso/sp/handlelogon

Recipient: https://A000000A.mobicontrol.cloud/mobicontrol/sso/sp/handlelogon

Log Out URL: https://A000000A.mobicontrol.cloud/MobiControl/sso/sp/handlelogout

Note: Ensure that the SAML information and SCIM schema information have the same case for MobiControl's FQDN. For example, if the SAML information has a000000a.mobicontrol.cloud whereas the SCIM schema has A000000A.mobicontrol.cloud, you may experience issues with assigning roles to the SOTI MobiControl application in SOTI Identity. To correct this, both the SAML and SCIM must have the exact same information and not have a case mismatch.