MS Authentication users and user group sync issues related scheduler windows service
MS Authentication users and user group sync issues related scheduler windows service
As we migrated our DVLS from on-prem to Azure, we also made a transition from SQL Server (using integrated authentication) to Azure SQL (using SQL authentication). During this migration we kept running the Devolutions Scheduler with a service account, just like in the old environment, as we sat up the MS authentication config in Administration > Server settings > Authentication > Microsoft Authentication. The only difference is that the service account is a local account on the new VM, we ran the old service with a domain account.
We don't want to use a local service account since it just adds to the complexity, but when we try to run the scheduler using LOCAL SERVICE, but the Microsoft Authentication users and user group sync fails with:
Failed to get Azure AD / Entra ID token for Graph API
ClientSecretCredential authentication failed: Request to the endpoint timed out.Please advice
Best Regards,
Simon
All Comments (10)
Hello,
Thank you for reaching out!
My name is William and I'm here to assist you in any way I can.
These issues are usually caused by the Local Service account being a very restricted account with minimal network privileges. You can try to run the service with Local System instead, which should have sufficient rights to use Microsoft authentication in Devolutions Server.
Best regards,
Hello,
Thank you for reaching out!
My name is William and I'm here to assist you in any way I can.
These issues are usually caused by the Local Service account being a very restricted account with minimal network privileges. You can try to run the service with Local System instead, which should have sufficient rights to use Microsoft authentication in Devolutions Server.
Best regards,
Hey,
Changed to LOCAL SYSTEM and also ran a reset of the Server cache -> MS authentication, but it didn't help, same error.
Regards,
Simon
Hello,
Would it be possible to confirm your Devolutions Server version?
First, we would like to confirm some information from the Devolutions Server Console:
Confirm that you changed the authentication to the DB from Windows to SQL users in the Devolutions Server Console under Edit > Database?
Could you confirm if the Management tools, Scheduler service and Web application are using the same account under the Advanced credentials?
We would also like to confirm the settings under Administration > Server Settings > Authentication > Microsoft authentication.
Could you verify that your secret is still valid?
Do you have the "Use specific client ID for users and user groups cache" enabled?
Feel free to reach out if you have any questions or need further clarification.
Best regards,