This article provides guidance on correctly formatting *.csv files for import into SOTI Identity, helping to prevent errors during user creation.
The "No Such Host is Known" error in SOTI MobiControl occurs due to a misconfiguration when SOTI Identity has not been selected as the authentication option. The web console shows "Server Error" when logging in.
When SOTI Identity is configured with Microsoft Entra ID and utilized in conjunction with SOTI MobiControl for device configurations, setups, enrollments, and shared devices, failures are observed.
This article addresses the issue where some users do not receive an email after selecting "I Forgot Company ID" on the SOTI Identity login page. It explains the underlying behavior and provides a workaround resolve the problem.
This article summarizes the issues observed after an upgrade to SOTI Identity 2025.0.0.
This article explains adding Dropbox as a third-party SAML application for single sign-on (SSO) to SOTI Identity.
This article provides a detailed guide on how to manually transfer a SOTI MobiControl instance from one SOTI Identity tenant to another for the purpose of Single Sign-On (SSO).
How to configure SOTI Identity after migration of SOTI MobiControl from one server to another.
This article details the steps required to configure Multifactor Authentication in SOTI Identity.
This is a mock article that demonstrates the steps needed to integrate the SOTI MobiControl application into SOTI Identity.
This is a mock article that demonstrates how to assign applications and roles to users in SOTI Identity.
Authentication to SOTI ONE Platform applications is not working via SOTI Identity where an Azure AD connection is configured due to expiry of refresh token. Azure AD refresh token expired, that needs reauthentication. To resolve the SOTI Identity login issue, follow these steps - <span class="TextRun SCXW672004 BCX0" lang="EN-US" xml:l
Authentication to SOTI ONE Platform applications is not working via SOTI Identity where a 3rd party IdP has been configured due to an expired SAML certificate. SOTI Identity’s SAML Certificate will be renewed on Sep 17, 2022. 3rd party IdP’s such as Okta, OneLogin, AzureAD should automatically adjust to the new SAML certificate. Should the automatic adjustment fail, ma
Authentication to SOTI ONE Platform applications is not working via SOTI Identity where a 3rd party IdP has been configured due to an expired SAML certificate. SOTI Identity’s SAML Certificate will be renewed on October 16, 2021. 3rd party IdP’s such as Okta, OneLogin, AzureAD should automatically adjust to the new SAML certificate. Should the automatic adjustment fail, manual r
Users are not able to log in using their IdP credentials after the new release of SOTI Identity (v1.1 released on 6th June 2020). This issue affects customers who have integrated IdP with SOTI Identity prior to 6th June. In this new release, SOTI Identity has brought support for IdP initiated login. It means that after integration of SOTI Identity with an IdP, users&n
: If SOTI Customers have been issued two or more identity tenants and SOTI MobiControl is configured and bound with one tenant of SOTI Identity, how to link or configure MobiControl with another tenant of SOTI Identity. In order to link SOTI MobiControl with the second tenant of SOTI Identity, We would need to delink existing tenant from MobiControl. We would need following details to do so: MobiControl
SOTI has released SOTI Identity to provide users with simple and secure access to the SOTI ONE Platform suite of solutions, including SOTI MobiControl. To use SOTI Identity, MobiControl customers would be required to integrate SOTI Identity. To configure SOTI Identity with SOTI MobiControl, please follow the steps mentioned in the below video. In case, you have started with SOTI MobiControl version 15.0.0 and above, SOTI Identity will be automatically configured with SOTI Mo
