DVLS Auth Error

Implemented

DVLS Auth Error

avatar
Andreas

DVLS 2023.1.8.0 / 2023.2.2.0

RDM

Hi All

I've installed a new Windows Server 2022 (21H2) and DVLS 2023.2.2.0 (also tried it with 2023.1.8.0) which will be used as Test System.

Database is running on a remote SQL 2016 Server.

Only AD and Azure Auth are configured, which both are working fine (same Config as on Productive System which works).

AD/RDM Problem:

AD Diagnostics are working, Groups and Users can be imported.

The specific User is imported in RDM.

AD Auth via Web works, but via RDM im not able to login with the AD User:

Azure Problem:

Microsoft Authentication is configured 1:1 as in Productive System and Test Connection is positive:

The specified Azure App has both URL's for Redirect URI's configured (Prod and Test).

But im not able to Login via Azure:

The Logs show Regional Setting Problems:

So i tried it by changing the regional Settings from "German/Switzerland" to "English/Switzerland" and "English/United States", without Luck.

Also a reboot after changing the Regional Settings doesnt work nor a completely DB Wipe and fresh Installation of DVLS after chaning the Regional Settings doesnt work.

Ive tried all those Steps (inclusive DB Wipe and Reinstall) with DVLS 2023.1.18.0 and DVLS 2023.2.2.0

Complete Error Message:

ArgumentException - Customized cultures cannot be passed by LCID, only by name. (Parameter 'culture')

   at System.Globalization.RegionInfo..ctor(Int32 culture)
   at Devolutions.Server.Common.CultureInfoUtils.<>c.<TryGetCountryCodeFromCountryName>b__0_0(CultureInfo x)
   at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
   at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Func`2 predicate, Boolean& found)
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at Devolutions.Server.Common.CultureInfoUtils.TryGetCountryCodeFromCountryName(String countryName)
   at Devolutions.Server.UserManager.UpdateFromAAD(UserEntity user)
   at Devolutions.Server.UserManager.DoAddUser(ISessionContext context, UserEntity user)

NullReferenceException:

NullReferenceException - Object reference not set to an instance of an object.

   at Devolutions.Server.Managers.AuthenticationProvider.SkipAuthentication(LoginContext loginContext)
   at Devolutions.Server.Managers.AuthenticationProvider.AuthenticateUser(LoginContext loginData, String userName, String password)
   at Devolutions.Server.Managers.AuthenticationProvider.ValidateUser(LoginContext loginData, String userName, String password, LoginAttemptEntity loginAttempt)
   at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.DoLogin(ISessionContext context, ParsedLoginParameter loginParameter, LoginContext& loginData)

Working Prod Sys:

Not working Test Sys:

Maybe a Problem of the .NET Lib?

Prod:

Test:

Any Thoughts?

Best Regards,

Andreas

All Comments (11)

avatar
Richard Boisvert

Hello Andreas,

For the AD authentication in RDM, could you please verify point 1 of https://docs.devolutions.net/kb/devolutions-server/how-to-articles/configure-windows-authentication/ ? If it is not enabled on the Devolutions Server side, Windows Authentication will not work in RDM. You can also check point 5-6 in the KB article.

For the Microsoft authentication issue, I have never seen that culture issue, no matter what regional setting is configured. Can you try to install the ASP.NET Windows hosting bundle instead?  https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.18-windows-hosting-bundle-installer

If it does not help, could you enable the debugging mode by going on the web interface of your Devolutions Server, under Administration --> Server Settings --> Logging - check Log debug information - save. Once enabled, try to use the Microsoft authentication again.

Could you then send us the server logs (on the web interface again, Reports --> Data Source Logs - Export) to service@devolutions.net .

You can turn off the debugging after.

Best regards,

Richard Boisvert

avatar
Andreas

Hi Richard

Thanks for your Inputs.

For the AD authentication in RDM, could you please verify point 1 of https://docs.devolutions.net/kb/devolutions-server/how-to-articles/configure-windows-authentication/ ? If it is not enabled on the Devolutions Server side, Windows Authentication will not work in RDM. You can also check point 5-6 in the KB article.

Everything is set as described in your Document, but Windows auth via RDM doesnt work.

The Test Environment is in the same Net as de Prod Server is. Also the Configurations is in my opinion 1:1 the same as in de Prod environment.

The only difference i notice is the newer OS (2019 -> 2022) and because i used the most current DVLS Console at beginning, the Setup installed .NET 7 instead of 6.

I will retry by uninstalling .NET 7 and install .NET 6 instead.

For the Microsoft authentication issue, I have never seen that culture issue, no matter what regional setting is configured. Can you try to install the ASP.NET Windows hosting bundle instead?  https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.18-windows-hosting-bundle-installer

I will try this also.

Thanks,

Andreas

Edit:

Sorry for the late Delay. But i've tested it and it still doesnt work. I need to activate the Debug Logs and will send it to you next week.

Best Regards and happy Weekend!

avatar
Richard Boisvert

Hello Andreas,

Thank you for the update, we will wait for the logs.

Have a great weekend as well!

Best regards,

Richard Boisvert