Access SignalR Service with AAD auth options started to fail after several months

aspnet / AzureSignalR-samples

Code samples for Azure SignalR

MIT License

330 stars 389 forks source link

Access SignalR Service with AAD auth options started to fail after several months #157

Open enijburg opened 3 years ago

enijburg commented 3 years ago

We have a couple .netcore applications connected to signalr services through aad auth. Last week the clients that connect to the negotiated endpoint get 401 errors. If I change the AddAzureSignalR connection string from the "Endpoint=https://nnn.service.signalr.net;AuthType=aad;" to the Primary connectionstring from Keys in azure portal everything works again. Did something change related to AAD auth?

Thanks in advance.

https://github.com/Azure/azure-signalr/pull/1243

terencefan commented 3 years ago

Hello, @enijburg when did this happen? And what type of managed identity you are using now?

[ ] System assigned
[ ] User assigned

terencefan commented 3 years ago

Would you mind tell me in which region you tested your service as well?

enijburg commented 3 years ago

Hi @terencefan, our services run in west europe and north europe. We assign User assigned managed identities through IAM role assignments from deployment pipeline (SignalR App Server (Preview) role)