No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
<pre id="tw-target-text" class="tw-data-text tw-text-large tw-ta" dir="ltr" tabindex="-1" role="text" data-placeholder="Traduction" data-ved="2ahUKEwjX79SM7eyQAxV3cKQEHSlLF54Q3ewLegQIDBAV" aria-label="Texte traduit : Hello, I hope you are well. I am writing to find out if other SOTI administrators are experiencing this issue in their companies. I have Samsung XCOVER 7 phones that are shared by several users on the same day. We have applications on these phones that require SSO authentication via Microsoft 365. When the phone is passed around, it is very difficult for the user to log in to these applications because SOTI Surf (or another browser) caches the last 365 login for SSO. I am forced to manually clear the app data and cache, but this is not manageable. Do you have any ideas for automating this more easily? Ideally, we would like to have profile-based management on these phones, but I don't know if that is possible. Thank you very much for your help. Have a good day,">Hello, I hope you are well. I am writing to find out if other SOTI administrators are experiencing this issue in their companies. I have Samsung XCOVER 7 (Android 15) phones that are shared by several users on the same day. We have applications on these phones that require SSO authentication via Microsoft 365. When the phone is passed around, it is very difficult for the user to log in to these applications because SOTI Surf (or another browser) caches the last 365 login for SSO.I am forced to manually clear the app data and cache, but this is not manageable. Do you have any ideas for automating this more easily? Ideally, we would like to have profile-based management on these phones, but I don't know if that is possible. Agent version : 2026.0.1 Build 1158Server version : 2025.0.2.1059 Thank you very much for your help. Have a good day,
Hello, I would like to register our Android devices with Microsoft via SSO. I have configured the group of devices so that colleagues have to register their phones with their Microsoft account when registering. However, after successful enrolment, SSO does not work for the O365 apps. There is a connection between Soti and Microsoft and I have also created a CA rule. Unfortunately, I still have to log in to each app individually. Does anyone have a solution here? Android 13 SamsungGalaxy xCover 5Soti Mobicontrol 2024
Hello all, i have allready activate SSO for Mobicontrol and now i want SSO for the Microsoft Apps like Outlook, Teams, etc. How can i set this up? We work with Samsung Galaxy XCover 5 and Android 13 on it. Soti Mobicontrol Version is 15.6.1. Thank you for you´re help.
Is there a way to enforce autologout of MS apps using the native android activity timer. We have shared devices that use MS apps, teams, outlook and another custom app that authenticates to Azure and we want to ensure that if a user forgets to log out that the device will after a period of time lapses.
Hi everyone, hope you are well. Just wanted to check if someone knows if SOTI MobileControl supports Single Sing On with a Microsoft 365 (AzureAD) account, not to the applications inside macOS, but to the computer login needed for the macOS itself. Like in the case of getting a new Mac - the device would be already pre-enrolled with SOTI via Business Manager, then the user would simply need their Microsoft 365 login details to SSO to their Microsoft 365 account and that same account to be used to create a local computer account on the Mac, instead of having two separate accounts. Hope you can help. Wish you all the best.
It just keeps redirecting to our SSO login. Is there a new URL that we should be using for 'no sso'? I want to make sure we're able to login with a local account before we switch from the AD graph over to Microsoft graph. This worked previously in v15.4.2 (https://soti.mobicontrol.com/MobiControl/WebConsole/?nosso=true). Thanks!
Hi Support-Team, I switched from internal user authentication to Active Directory based and it is working great, now I wanted to add SSO but cannot get it working. The website jumps to "Invalid response received from Identity Provider.", the server log shows "Invalid SAML 2.0 message. Element 'StatusCode' value is wrong. Expected 'urn:oasis:names:tc:SAML:2.0:status:Success' received 'urn:oasis:names:tc:SAML:2.0:status:Responder'". We are running ADFS 3.0, groups setting is set to Directory. Any ideas what went wrong? Thanks and cheers Carsten
Hey Folks, We are trying to setup SAML IDP using Azure ADFS, however we are getting a message saying "Invalid SAML 2.0 message. Response needs to be signed" However we have uploaded our most recent metadata file and we feel we have mapped our groups, names etc correctly and our response looks like it contains the correct information so we are a bit stumped. Can anyone shed any light on what could be causing this. Thanks David
Attempting to setup SSO to work with OKTA however I was running into an issue in which we receive the following error HTTP/1.1 405 Method Not AllowedContent-Length: 1665Content-Type: text/htmlServer: Microsoft-HTTPAPI/2.0X-Frame-Options: SAMEORIGINX-Content-Type-Options: NOSNIFF The data was initially imported with eh metadata file and the one thing that threw me off was the list attribute which I want sure what would be required for the field. I wasn't sure if that was the root cause but figured I would reach out here to see if anyone else had this before.
We just started using SOTI MC a month ago to allow for remote training and support to be possible on field personnel's company devices. My company has requested that our on prem Soti Mobi Control be accessible through OKTA for the support users. I have opened a ticket a couple weeks ago when our SSO admin was having issues configuring it in the web consol. I haven’t had much luck support wise with that subject(but some luck in other areas). So after getting another “has this been resolved yet” email, we decided to just try using what little info is in the guide. That was a mistake. The moment the “Enable SSO” box was checked and “OK” was pressed we were all kicked. I immediately responded to the ongoing email chain with Soti on the case regarding our SSO setup, got a response a day later, but only asking if the issue was resolved or not. (Update)I just received another response from support. They stated that I had several issues and a case needed to be made for each one. The original issue regarding the SSO(SAML) was replaced with one of the latter issues. I’ll have to open another case with support to have someone else start helping with the SSO issue. TLDR: SSO was activated but not configured properly, and now no one can log into the system to turn SSO off. Not sure what else we can do to recover the system. Anyone know what options we may have to get this back to a usable state? Chances are I won’t have access to do anything on the server or database side(I will have to speak to the departments instead), but if I knew what to say and ask for, that would help alot. On a side note, does support from Soti get better if you pay for Enterprise support? I am still trying to justify the extra expense to the bosses.
Can I use MobiControl to manage Single Sign-On for my applications?
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
