We have a Windows 2008 R2 server running MSSQL 2012 (11.0.7001), we are doing some testing to validate a database upgrade is working properly among our in use RDM clients. We haven't used the iOS version in a long time due to our DB version for RDM being out of date but now that we upgraded we cannot connect (doesn't seem to be DB related)
Authentication is "integrated" login scheme is DOMAIN\username
Doing a server test or a Database test both come back with what looks like a .Net error which begins with "Specified method is not supported. at Microsoft.Win32.SafeHandles.SafeGssNameHandle.CreatePrincipal (System.String name)" I cant write the entire error (its not short) and the context window doesn't allow text selection please see attachment.
Any support here is appreciated.
--
Eric Sakariasen
Connetic IT Support
2018-06-01.jpg
Hello,
What version of RDM Windows are you using?
What version of RDM iOS are you using?
Do you have a SSL certificate enabled on your SQL Server?
Best regards,
Jeff Dagenais
I am having the same issue as well. When trying to connect to my MS SQL data source w/ integrated security I receive the same error message.
I am using the following:
Device: iPhone 7 & iPad Gen 4
App Version: 4.7
No SSL cert enabled on SQL Server
How would find out the version of RDM Windows? Is that the data source version?
Thanks,
James
Hi,
I was able to reproduce the issue and currently investigating it.
Best regards
Mathieu Morrissette
Hi,
Unfortunately the third party we use to connect to MS SQL doesn't support connecting using integrated security anymore.
For the time being, the workaround would be to use SQL Server with Mixed Mode enabled.
We also have a product called Devolutions Server which supports multiple authentication modes including windows authentication.
Im really sorry about that.
Best regards
Mathieu Morrissette
Good to know. Thanks Mathieu. I'm guessing this is something you guys will be looking into resolving with the third party? If so, is there a way to be notified when that has been fixed?
Hi,
We are actively working to resolve the issue and we'll let you know when it'll be resolved.
The support for integrated security broke when they implemented support for SSL encryption.
Best regards
Mathieu Morrissette
Also having this error, following along so that I can be notified when it's resolved.
I went to check on our database connection, and we already use mixed, but still face the error.
Hi Patrick,
The workaround is currently to use mixed mode and connecting to the database using an SQL login.
Make sure the Login mode in your data source is set to Database login.
Best regards
Mathieu Morrissette
Hi Mathieu Morrissette
We have the same issue but due to security policy in our company we are not allowed to run with multi login.
Is there a time-frame for a fix?
Nick
Maersk Training A/S
Hi,
Unfortunately, the third party we use hasn't provided us with an ETA for the fix.
It might be a while since it is not an easy fix. I'm really sorry about that.
I'll keep you updated.
Best regards
Mathieu Morrissette
Support,
I really hope there is a lesson here that some level of testing is going to take place for all of the different database and with mechanisms. We are suffering at this point and since apple has no way to obtain a previous version all of our iOS users are dead in the water. If we didn’t have a support staff of 23 users actively using this software we may change to a different authentication mechanism. If it goes much longer we are going to be asking for a license extension.
Thanks for your time.
--
Eric Sakariasen
Connetic IT Support
Unfortunately I only discovered this feature and because we only use Windows Authentication, it's immediately unusable.
Please let me know when it's resolved.
Will Integrated Authentication work if we enable SSL encryption on the SQL Server connection?
Hi,
The SSL encryption works but integrated authentication is non-functional.
Best regards
Mathieu Morrissette
Hi,
unfortunately this also includes the Mac version which is not working with integrated authentication after upgrading to 5.5.0.0 or 5.5.1.0.
Will there be a fix? And if yes, when will it probably be available?
Thanks,
Markus
This have been going on for a long time. So they are not having focus on this part.
Our company have started to test 2 other products to find a solution, due to company policy...
It is sad as we find this software to be quit good but due to security reasons, force us to move to other provides.
Nick
Maersk Training A/S
Hi,
You can follow the issue status here : https://github.com/mono/mono/issues/9028
Best regards
Mathieu Morrissette
Hello,
If you are interested the integrated authentication works in version 5.4.0.0, here is the download link : https://cdn.devolutions.net/download/Mac/Devolutions.RemoteDesktopManager.Mac.5.4.0.0.dmg
Best Regards,
Etienne Lord
Wrong platform. This is about iOS, not macOS.
Hello,
Sorry for the confusion, I should've been clearer, the message was meant for Markusk
"
Hi,
unfortunately this also includes the Mac version which is not working with integrated authentication after upgrading to 5.5.0.0 or 5.5.1.0.
Will there be a fix? And if yes, when will it probably be available?
Thanks,
Markus
"
Etienne Lord
Why can’t you roll back your use of mono to the previous working version? You can easily see that the mono developers are not going to be fixing this in the near future.
--
Eric Sakariasen
Connetic IT Support
Hi,
Unfortunately, Xamarin.iOS is deeply linked with mono and to rollback mono we would also need to roll it back.
Rolling it back would prevent us from supporting the newer releases of iOS.
Best regards
Mathieu Morrissette
Hello Etienne,
thank you for clarifying. Since iOS and MacOS are close and I couldn't find the corresponding forum, I posted my question here.
Where should I put my post concerning MacOS?
Thanks,
Markus
@markusk,
You can post any issue/question related to RDM Mac on this forum
https://forum.devolutions.net/forum44-remote-desktop-manager-mac--support.aspx
Best regards,
Jeff Dagenais
Update?
The issue has been closed on Github for a month.
--
Eric Sakariasen
Connetic IT Support
Hi,
The fix will be included in mono 5.18. Xamarin is currently, on the stable branch, using mono 5.12.
They don't have any yet ETA but I'll let you know when the fix will be available.
Best regards
Mathieu Morrissette
Hi,
The issue is still there but the github issue is closed.
We can't use the local credentials because we use AD accounts already with the private vault.
We need an ETA or any roadmap to be able to connect on iOS.
Thanks
RemoteDesktopManager.log
Hi,
Mono 5.18 is not yet released. Here's the release page : https://www.mono-project.com/docs/about-mono/releases/
Best regards
Mathieu Morrissette
Did you try to work around the Mono/AD Auth issue over the past eight months, or just twiddle your thumbs while waiting for someone else to fix it? The lack of sense of urgency from your company doesn't inspire confidence.
In any event, 5.18 is out. What's the ETA for an updated Mac client?
https://www.mono-project.com/docs/about-mono/releases/5.18.0/
Hi Steve,
The fix is not yet included in the xamarin framework but should be very soon.
I'll keep you updated for any development.
Best regards
Mathieu Morrissette
Given your lack of urgency with this issue, what assurance do we have that the next time Mono or xamarin break something that there will be a solution in a reasonable timeframe?
Hi Steve,
We have other data source types such as the Devolutions Password Server that is much more stable than the SQL Server connector provided by mono.
Once Xamarin Framework includes the newly released mono, we will test it to see if the fix is working and that nothing else broke and release a new iOS build as soon as we can.
Apple doesn't allow to install an older version of the software It would have been very useful.
Best regards
Mathieu Morrissette
Do you have another product that has Active Directory integration that doesn't cost us additional?
--
Eric Sakariasen
Connetic IT Support
Well, I'm specifically worried about the Mac version, but since the root cause is the same and this thread was more active I piled on here. I'd just like some assurance that the next time something breaks you'll actually take it seriously, unlike this issue. It is unreasonable that my network guy contacted you for support regarding a bug and the answer was to upgrade the client, which we had to hold back because you didn't put any effort into fixing this issue. At no time until a support chat I held yesterday were we offered any other way forward (Devolutions Server).
What I'm not clear on is if the Devolutions Server is included with our RDM license or not. If it is *not* then you're trying to upsell us after removing features that we paid for with our product. That's shady at best.
I have been upset to see that this issue is still not resolved 7-8 months later.
I really hope that we can get the ball rolling with this resolve soon.
I understand that we are a small portion of the user base, however I've not been able to use my license on the Mac for months now.
Status?
The 1/14 Xamarin update (5.2.1.13) includes Mono 1.8 support. Can we get a status update?
https://docs.microsoft.com/en-us/xamarin/mac/release-notes/5/5.2
Thanks,
Steve
@Mathieu Morrissette - Seems like we aren't getting replies here for the past several questions.
--
Eric Sakariasen
Connetic IT Support
Hi,
The release notes for Xamarin.Mac 5.2.1.13 are actually misleading. While the message only says that Xamarin.Mac supports Mono 5.18, clicking on the GitHub issue shows us that it's only a fix for the Unsupported Framework of Xamarin.Mac. RDM Mac does not use the Xamarin.Mac Unsupported Frameworks because, as the name implies, this is not actively supported by Xamarin/Microsoft. Switching from the Full (currently used) to the Unsupported would not be a simple undertaking as this could affect the whole applications in unexpected ways.
With the Unsupported Framework we can actually build Xamarin.Mac with any Mono framework (with all the potential issues that this could bring). Xamarin.Mac supported frameworks (Modern and Full) both comes with a bundled version of Mono (currently 5.14) which cannot be changed.
Best regards,
Xavier Fortin
Looking for an update again... Stay with us, folks.
Any update on this. We have no option but to use AD accounts to connect to SQL and RDM is worthless if you can not connect to a database.
Mono 5.18.0 was released 21 December, and I'm still getting the "Specified method is not supported" error.
Does anyone have this working?
Hi,
As you can see here: https://github.com/mono/mono/issues/9028#issuecomment-460268133
The issue hasn't actually been solved in Mono 5.18. And we do not know yet when Mono 5.20 will be released. That being said, the release of a new Mono version in no way guarantees it being integrated into Xamarin soon after.
I'll try to build a separated version with Unsupported Frameworks + Mono 5.20 when available, but I cannot guarantee the success of the endeavor (and it cannot be done for iOS and Android).
Best regards,
Xavier Fortin
I see, thanks!
When you say cannot be done for iOS/Android, does that mean the feature will never be supported or just that we'll have to wait for framework support?
Hi,
I only mean that there is no Unsupported Frameworks option that allows choosing a specific Mono version in Android and iOS that I am aware off. Which means that we have to wait for Microsoft to integrated Mono 5.20 into Xamarin.Android and Xamarin.iOS before this can be brought back to RDM Android and RDM iOS.
Best regards,
Xavier Fortin
Gotcha, good reply - I'll hope for the best then, and advocate for external display and mouse support in RDM for IOS in the meantime :)
Thanks
Acknowledging first that I'm not a dev, but is there not a way to call another library for authentication? Your Devolutions server product allegedly offers AD logon; why not have a little daemon running that code playing middleman between the Mac version of RDM and the SQL data source? Or, give us small app to run on the SQL server to handle those requests, something like that. I'm sure a bunch of smart guys like you could come up with a solution in under a year, especially when it seems like you have all of the building blocks in place.
Anyone thats (not)patiently waiting for this like my entire company can watch the releases here:
http://releases.xamarin.com/
I'm curious though are we waiting for a GM or are we waiting for any release?
--
Eric Sakariasen
Connetic IT Support
We also are required to use Integrated Authentication. This bug prevents our staff from responding to emergency infrastructure outages from a remote location. Hoping this get resolved soon. Thank you.
Considering it's been almost a year and they've put zero effort into fixing it, I wouldn't count on it.
I cannot believe this is still not resolved.
I have an extra license for my work Mac when I use it and it is going to waste.
Hello,
Since December 2018 we are waiting Mono 5.20.0 release. The release can be followed at https://www.mono-project.com/docs/about-mono/releases/ and after Xamarin will be able to integrate it.
I look with Mono and they are currently working on many issues, the latest update was 4 hours ago with 5.20.1 release.
Good news is that the fix seems to be already there (see #9028 here)
Many customers and many other software companies are waiting for this fix. As soon as it is releasing we will implement it.
Best regards,
David Grandolfo
Any updates on this? It was released last month.
Hi,
The latest version of Xamarin.IOS is version 12.10. This version integrates Mono 5.18. We cannot fix the problem until Microsoft builds a new version of
Xamarin.IOS with Mono 5.20.
Best Regards,
Nicolas Dufour
It's been a freaking year - let's pretend that they're *never* going to fix it (given that you guys have been saying "soon" for that entire year). At what point do you take responsibility for making your own product work? Hit the war room and start coming up with other options (such as lifting the functionality from your other products or redesign the client, or something! I know when we're up for renewal I'll be strongly recommending we switch vendors specifically because of this issue and your uncaring and lackadaisical attitude.
Hello, Xamarin.iOS 12.99 is out with Mono 6.0. Any news?
Hi,
This is next on our list, we will be checking out the patch shortly to see if it includes the fix we have been waiting for.
Best Regards,
Bea Racine
Bracine
Has this been looked at yet? I know it has only been 2 days but this is the hot item.
Hi,
We are looking at it right now. It's not clear yet if the Framework update has everything we need to fix integrated security, if it does they've changed how it works significantly. it will take some time to fully investigate this.
Best Regards,
Bea Racine
Any update.... been 29 days now.
Hi,
After investigation, it is not possible to implement integrated security with the framework update.
Best Regards,
Nicolas Dufour
Hi Nicolas,
I wanted to ask if its not possible to implement a solution with this update or is it generally not possible?
Hi,
It hasn't been possible since early 2018 (Mono 5.10) and it is still not possible. For it to work, Microsoft has to fix the problem.
Best Regards,
Nicolas Dufour
It hasn't been possible since early 2018 (Mono 5.10) and it is still not possible. For it to work, Microsoft has to fix the problem.
Bonjour Nicolas,
Is there a link to the MS GitHub issue about this (assuming there is one) so we can follow on it?
Merci!
Hi Pascal,
Here is the link: https://github.com/mono/mono/issues/15973
Best Regards,
Nicolas Dufour
Any news on this one?
No solution yet,
Best Regards,
Nicolas Dufour
And since the last message the option for integrated security has been entirely removed from the iOS version, correct?
Any chance of seeing it return in the future?
Hi Patrick,
Yes, it has been removed, and there are no plans to support it in the near future unless Microsoft incorporates this functionality into the .NET framework.
Best Regards,
Nicolas Dufour