Shared secret authorization with Azure SignalR Service
While testing out Azure Functions development and configuration with Azure SignalR Service, I needed a very simple key-based (shared secret) authorization mechanism so that my console-based SignalR client could connect to my Azure SignalR Service-powered hub using a very simple mechanism.
The docs and the sample showcased the negotiate
endpoint returning the connection info directly:
But a stackoverflow answer pointed me to the solution: just the proper IActionResult
using OkObjectResult
with the connection info when the access key is properly validated:
PreviousExploring Azure Data with Kusto and DashboardsNextUsing Azure File Copy from DevOps yaml pipeline
Last updated