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.
