DVLS Auth Error

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,

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!

Hello Andreas,

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

Have a great weekend as well!

Best regards,

Hey Richard

I've activated Debug Logs last Week and did some attempts today.

Funny Thing:
Logins via Webinterface now both Works for AD and Azure. Whyever, because i've changed nothing since Server Setup last Week.

I've tested more RDM Attempts directly from the Server and from a remote Client.
From the Remote Client, when i select "Always as username" then every Mechanism is working via RDM.
But "Use Windows authentication" still doesnt work in RDM (from Remote Client and local on the DVLS Server).
It only shows the Message "Could not connect current user to DVLS. Please see DVLS logs for more details".

After this Error Message, there are no Logs available in Console!

On the Server itself, if i switch in the RDM Datasource Settings from "Use Windows authentication" to "Always ask username" and try to Login via AD, i've the Error bellow. But there is an interesting Log entry available now:


Complete Log Message:

DomainConfigurationNotFoundException - Domain configuration id '3cfcd539-199a-4ae7-80b4-e549169e0e0d' could not be found.

   at Devolutions.Server.ActiveDirectory.ActiveDirectoryFactory.Get(Guid domainId, ActiveDirectoryFactoryParameters parameters)
   at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.UserResolver.FindDomainUserFromLoginParameter(UserEntity userEntity)
   at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.UserResolver.FindDomainUser(UserEntity userEntity)
   at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.UserResolver.Resolve()
   at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.FindUser(ISessionContext context, ParsedLoginParameter loginParameter)
   at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.CreateLoginContext(ISessionContext context, ParsedLoginParameter loginParameter)
   at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.DoLogin(ISessionContext context, ParsedLoginParameter loginParameter, LoginContext& loginData)

This Message is more than interesting, because the AD Connection is working:


Azure is also working:


If i switch to the Productive System, everything is working normal.
Please notice: Same Account works from a remote Machine and it is already existent in Administration > Users.

I've now again updated to DVLS 2023.2.2.0.
From Remote Machine, "Use Windows authentication" works with my AD User.

Long story short: It looks like that only "Use Windows Authentication" is not working from the Server itself right now.
Everything else is working now (absolutely Magic for me).

Thanks,
Andreas

Hello Andreas,

Could you confirm if the staging server is on a server that is domain joined? If not, it may explain why the "Use Windows Authentication" is not working in RDM.

We may need to verify some settings in the SQL Server database, however, so I would recommend having a session to verify it. If you are interested, please write to service@devolutions and reference this topic.

Best regards,

Hello Andreas.

I don't know if it will be relevant for you but I have the same problem as you about Culture.
See my post...I found a workaround.
https://forum.devolutions.net/topics/39819/azure-groups-and-users--auto-create

Regards,
Alexandre Diez

Hello Andreas,

I have linked the engineering ticket to this case, we will notify you once the fix is in place.

Best regards,

Any update?

Hello,

The ticket is still in the backlog of the engineering team, but they are aware of the issue and have a potential fix for it.

Best regards,

Hello,

The engineering has found the source of the issue, the fix will be included in the upcoming release, 2023.2.5.

Best regards,

Hello Andreas,

The 2023.2.5 version of Devolutions Server is now available, with the fix - https://devolutions.net/server/release-notes/

Best regards,