Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
enijburg opened this issue Apr 9, 2021 · 3 comments

Comments

@enijburg
Copy link

enijburg commented Apr 9, 2021

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.

Azure/azure-signalr#1243

@enijburg enijburg closed this as completed Apr 9, 2021
@enijburg enijburg reopened this Apr 9, 2021
@terencefan
Copy link
Contributor

terencefan commented Apr 21, 2021

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

  • System assigned
  • User assigned

@terencefan
Copy link
Contributor

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

@enijburg
Copy link
Author

enijburg commented Apr 21, 2021

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants