There's a new home for Articles. Find Articles on Our Product Support Page.
Hi As we know, in MobiControl, there's an option to assign both a user from Identity or an LDAP (AzureAD, Okta, etc). For our purposes, we use Okta. We have managed to create an application in Okta to create the SAML for authentication/authorization. This part is fine because we can pull some users from Okta. And that is precisely the problem. We cannot find all of the Okta users when trying to assign a user to a device from the MobiControl Dashboard. Is there any troubleshooting I can do there? In my opinion, the integration is done correctly, otherwise I wouldn't be able to find anyone. Thanks a lot
Does SOTI have any plans to support SCIM for user provisioning from Okta to Mobicontrol? https://developer.okta.com/docs/reference/scim/
https://share.getcloudapp.com/2NuXvkZD Is there a support for Okta federated accounts with iOS BYOD (user enrollment) add device rules? It appears a single option with MS Azure directory.
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.
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