Negotiated url is not working while connecting to Azure webpubsub for socketio

Question

Negotiated url is not working while connecting to Azure webpubsub for socketio

Devender Singh 25

I have a client and .net API and an azure webpubsub resource for socketio. I am trying to connect to pubsub via negotiated url.
Clinet (js) hits '/negotiate' endpoint of APi which generates negotiated url using

        _webPubSubServiceClient = new WebPubSubServiceClient(hubConnectionString, "socketio"); // Specify the hub name as "chat"

var uri = _webPubSubServiceClient.GetClientAccessUri(
            userId: "Dev");

        var url = uri.AbsoluteUri.Replace("https://", "");

        return Ok(new { url });

The negotiate url recieved by client is

'wss://azurepubsubforsocketio.webpubsub.azure.com/client/hubs/socketio/access_token=<....>'

While the 'Client URL generator' in pub sub resource shows below

User's image

where path is '/Clients/socketio/hubs/socketio' which doesnot match with negotiated url format as mentioned before.

That is the issue, now client is not able to connect to pubsub.
And got below error in tracing tool:

{"time":"2025-03-18T04:03:17.8239513Z","logLevel":"Error","eventName":"AudienceValidationFailed","message":"Failed to validate audience. Expected Audiences: azurepubsubforsocketio.webpubsub.azure.com/clients/socketio/hubs/socketio, azurepubsubforsocketio.webpubsub.azure.com:443/clients/socketio/hubs/socketio. Actual Audiences: https://azurepubsubforsocketio.webpubsub.azure.com/client/hubs/socketio.","exception":null,"ip":"2401:4900:1cb2:859c:817c:a5c:2ceb:9d62"}

The actual audiance is coming from negotiated url generate by azure sdk, suggest me solution.

Prabhavathi Manchala 2,315 Reputation points Microsoft External Staff Moderator

2025-03-18T06:33:06.65+00:00
Hi Devender Singh,

The error happens because the path in the generated client access URL does not match the audience expected by Azure Web PubSub for Socket.IO.

var uri = _webPubSubServiceClient.GetClientAccessUri(userId: "Dev"); var url = uri.AbsoluteUri.Replace("https://", "").Replace("/client/hubs/socketio", "/clients/socketio/hubs/socketio:443"); return Ok(new { url });

Make sure you are using the latest version of the Azure.Messaging.WebPubSub SDK. If you are using an older version, update it through NuGet as below.

dotnet add package Azure.Messaging.WebPubSub --version latest

Ensure cross the configuration of your WebPubSub resource in Azure. Ensure that the hub name (socketio) is correctly mapped and that it expects connections in the correct format.

Please try to manually construct the URL as shown below.

wss://azurepubsubforsocketio.webpubsub.azure.com/clients/socketio/hubs/socketio/access_token=<....>

Kindly refer below document for Client Endpoint and Client Path.

https://learn.microsoft.com/en-us/azure/azure-web-pubsub/socketio-quickstart#write-client-code

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Devender Singh 25 Reputation points

2025-03-18T18:42:27.2033333+00:00
Hello @Prabhavathi Manchala
couple of things,

why I need to apply this quick fix, are they recommended in Production apps? given that my pkgs are up to date.
var uri = _webPubSubServiceClient.GetClientAccessUri(userId: "Dev");

var url = uri.AbsoluteUri.Replace("https://", "").Replace("/client/hubs/socketio", "/clients/socketio/hubs/socketio:443");

return Ok(new { url });

The doc url you shared, it doesnot help with .net pubsub sdk using negotiated url which is a recommended approach but Microsoft has not mentioned/elbarated the configuration process with .net and negotiated url, just providing quick samples around node js.

After making the quick fix, pubsub is not able to invoke the event handlers in API side. Since there is no proper guidance in Microsoft docs for that, I am putting my snippets below with current error, if anything can be worked out:

Program.cs - pubsub configs

builder.Services.AddWebPubSub(o => { o.ServiceEndpoint = new WebPubSubServiceEndpoint(connectionString); }) .AddWebPubSubServiceClient<Hub>();

app.MapWebPubSubHub<Hub>("api/eventhandler");

My HubClass:

Hub.cs

sealed class Hub : WebPubSubHub { private readonly WebPubSubServiceClient<Hub> _serviceClient; public Hub(WebPubSubServiceClient<Hub> serviceClient) { _serviceClient = serviceClient; } public override Task OnConnectedAsync(ConnectedEventRequest request) { Console.WriteLine($"[SYSTEM] {request.ConnectionContext.UserId} joined."); return Task.CompletedTask; } public override async ValueTask<UserEventResponse> OnMessageReceivedAsync(UserEventRequest request, CancellationToken cancellationToken) { // Create message data var messageData = new { from = request.ConnectionContext.UserId, message = request.Data.ToString() }; // Convert to JSON var json = JsonSerializer.Serialize(messageData); // Use the simplest overload of SendToAllAsync await _serviceClient.SendToAllAsync(json); return new UserEventResponse(); } }

Error:
In tracing tool:

Failed invoking 'tunnel:/eventhandler/' for 'hub:socketio,event:connect,type:sys,category:connections,requestType:Connect'. ClientRequestId: 'bde94c5c-3b3f-471d-b435-dc0190cd9ce9'.

Unexpected status code for 'handshake'. StatusCode: 500. ClientRequestId: 'd8eb06af-7a1a-4d05-a590-e1c2fc2eb9fc'. Details: Get error from upstream: 'Client connection: -HBo-4tWyJ4Pc3zUooBIPwBWCyJwu02 failed to route as there's no server connection.'

If possible pls let me know what is missing, I am on this things for couple of days just to make a running connection, but not able to proceed bcs of these config issues.

Prabhavathi Manchala 2,315 Microsoft External Staff Moderator

Hi Devender Singh,

Apology for your inconvenience.

To apply this quick fix, the issue is that Azure Web PubSub for Socket.IO has a different client connection path compared to the default Web PubSub connections. The Azure SDK does not handle this correctly for Socket.IO (at least in the .NET SDK), which is why we need to manually fix the negotiated URL.

However, applying .Replace("/client/hubs/socketio", "/clients/socketio/hubs/socketio:443") not a recommended for production and you can remove the port 443.

please use below code.

var uri = _webPubSubServiceClient.GetClientAccessUri(userId: "Dev");
var url = uri.AbsoluteUri.Replace("/client/hubs/socketio", "/clients/socketio/hubs/socketio");
return Ok(new { url });

Failed invoking 'tunnel:/eventhandler/' & failed to route as there's no server connection. Indicates that your API is not properly connected to Web PubSub.

Please update your .NET negotiated URL generation to manually construct the URL using the correct format as below.

var token = _webPubSubServiceClient.GenerateClientAccessToken(userId: "Dev");
string correctUrl = $"wss://azurepubsubforsocketio.webpubsub.azure.com/clients/socketio/hubs/socketio?access_token={token}";
return Ok(new { url = correctUrl });

Make sure the API properly registers WebPubSub for Socket.IO, modify your Program.cs as shown below.

builder.Services.AddWebPubSub(o =>
{
    o.ServiceEndpoint = new WebPubSubServiceEndpoint(connectionString);
})
.AddWebPubSubServiceClient<Hub>(); 
var app = builder.Build();
app.MapWebPubSubHub<Hub>("/eventhandler");
app.Run();

Make sure to use app.MapWebPubSubHub<Hub>("/eventhandler"); instead of app.MapWebPubSubHub<Hub>("api/eventhandler");
Modify your Hub.cs as below

sealed class Hub : WebPubSubHub
{
    private readonly WebPubSubServiceClient _serviceClient;
    public Hub(WebPubSubServiceClient<Hub> serviceClient)
    {
        _serviceClient = serviceClient;
    }
    public override async Task OnConnectedAsync(ConnectedEventRequest request)
    {
        Console.WriteLine($"[SYSTEM] {request.ConnectionContext.UserId} joined.");
        await Task.CompletedTask;
    }
    public override async ValueTask<UserEventResponse> OnMessageReceivedAsync(UserEventRequest request, CancellationToken cancellationToken)
    {
       // Create message data
        var messageData = new
        {
            from = request.ConnectionContext.UserId,
            message = request.Data.ToString()
        };
		// Convert to JSON
        var json = JsonSerializer.Serialize(messageData);
        
        await _serviceClient.SendToAllAsync(Request.ContentType ?? "application/json", BinaryData.FromString(json));

        return new UserEventResponse();
    }
}

Dockerfile needs to properly expose the necessary ports and ensure correct API port is exposed.

  FROM mcr.microsoft.com/dotnet/aspnet:8.0
  WORKDIR /app
  COPY . .
  EXPOSE 8080
  ENTRYPOINT ["dotnet", "YourApp.dll"]

Prabhavathi Manchala 2,315 Reputation points Microsoft External Staff Moderator

2025-03-20T00:50:55.8066667+00:00

Hi Devender Singh,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Devender Singh 25 Reputation points

2025-03-20T03:37:23.0733333+00:00

Hi Prabhavathi Manchala

PFB

error CS1061: 'WebPubSubServiceClient' does not contain a definition for 'GenerateClientAccessToken'

and still getting below trace:

Failed invoking 'tunnel:/eventhandler/' for 'hub:socketio,event:connect,type:sys,category:connections,requestType:Connect'. ClientRequestId: 'ddec0c2c-0cfa-47c7-b68a-627af1907c69'.

Looking for 'how to setup pubsub and server' connection in .net for socketio pubsub

Sampath 3,750 Microsoft External Staff Moderator

Hello @Devender Singh,

Apology for your inconvenience.

can you please try below code

Server


using Microsoft.AspNetCore.Mvc;

using Azure.Messaging.WebPubSub;

using Microsoft.Extensions.Configuration;

using Microsoft.Extensions.Logging;

using System.Threading.Tasks;

[ApiController]

[Route("api")]

public class WebPubSubController : ControllerBase

{

    private readonly WebPubSubServiceClient _webPubSubServiceClient;

    private readonly ILogger<WebPubSubController> _logger;

    public WebPubSubController(IConfiguration config, ILogger<WebPubSubController> logger)

    {

        var connectionString = config["AzureWebPubSub:ConnectionString"];

        var hubName = config["AzureWebPubSub:HubName"];

        _webPubSubServiceClient = new WebPubSubServiceClient(connectionString, hubName);

        _logger = logger;

    }

    [HttpGet("negotiate")]

    public IActionResult Negotiate()

    {

        try

        {

            var uri = _webPubSubServiceClient.GetClientAccessUri(userId: "Dev");

            var correctUrl = uri.AbsoluteUri.Replace("/client/hubs/socketio", "/clients/socketio/hubs/socketio");

            _logger.LogInformation($"Negotiated URL: {correctUrl}");

            return Ok(new { url = correctUrl });

        }

        catch (Exception ex)

        {

            _logger.LogError($"Negotiation error: {ex.Message}");

            return StatusCode(500, "Error generating negotiation URL.");

        }

    }

    [HttpPost("send")]

    public async Task<IActionResult> SendMessage([FromBody] MessageRequest request)

    {

        if (string.IsNullOrWhiteSpace(request.Message))

        {

            return BadRequest("Message cannot be empty.");

        }

        await _webPubSubServiceClient.SendToAllAsync(request.Message);

        _logger.LogInformation($"Message sent: {request.Message}");

        return Ok(new { status = "Message broadcasted" });

    }

}

public class MessageRequest

{

    public string Message { get; set; }

}

enter image description here

Client


process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0"; // Disable SSL verification (dev only)

const io = require("socket.io-client");

const axios = require("axios");

const readline = require("readline");

// Function to get negotiation URL

async function connectToWebPubSub() {

    try {

        const response = await axios.get("https://localhost:7015/api/negotiate");

        const webPubSubUrl = response.data.url;

        console.log("Connecting to:", webPubSubUrl);

        const socket = io(webPubSubUrl, {

            path: "/clients/socketio/hubs/socketio",

            transports: ["websocket"]

        });

        socket.on("connect", () => {

            console.log("Connected to Web PubSub for Socket.IO");

        });

        socket.on("disconnect", () => {

            console.log("Disconnected from Web PubSub for Socket.IO");

        });

        socket.on("message", (msg) => {

            console.log("Received:", msg);

        });

        // Setup CLI input to send messages

        const rl = readline.createInterface({

            input: process.stdin,

            output: process.stdout

        });

        rl.setPrompt("Enter message: ");

        rl.prompt();

        rl.on("line", async (message) => {

            if (message.trim()) {

                try {

                    await axios.post("https://localhost:7015/api/send", { message });

                    console.log("Message sent!");

                } catch (error) {

                    console.error("Failed to send message:", error.message);

                }

            }

            rl.prompt();

        });

    } catch (error) {

        console.error("Error connecting to Web PubSub:", error.message);

    }

}

connectToWebPubSub();

enter image description here

If you have more questions, click Comment.

Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-22T10:36:19.1366667+00:00

Hello @Devender Singh ,have you checked the above comment?

Devender Singh 25

Hello @Sampath, @Prabhavathi Manchala
I guess the above flow is bypassing the webpubsub and client is directly hitting server via http post. I am looking for proper way of clients sending messages via pubsub.
So yes it didnot solved the problem.
here is my complete code:

PubSubController.cs

using Microsoft.AspNetCore.Mvc;
using Azure.Messaging.WebPubSub;


[ApiController]
[Route("api/v1/[controller]")]
// This endpoint provides the clients the URL to WebPubSub to hit.
public class PubSubController : ControllerBase
{
    private readonly WebPubSubServiceClient _webPubSubServiceClient;
    private readonly string hubConnectionString;  // WebPubSub resource connection string in Azure

    public PubSubController(IConfiguration configuration)
    {
        hubConnectionString = configuration["WebPubSubConnectionString"];
        _webPubSubServiceClient = new WebPubSubServiceClient(hubConnectionString, "socketio"); // Specify the hub name as "chat"
    }


    [HttpGet]
    [Route("negotiate")]
    public IActionResult Get()
    {

        var uri = _webPubSubServiceClient.GetClientAccessUri(
            userId: "Dev");

        var url = uri.AbsoluteUri.Replace("https://", "").Replace("/client/hubs/socketio", "/clients/socketio/hubs/socketio");

        return Ok(new { url });

    }
}

Hub.cs

using Microsoft.Azure.WebPubSub.AspNetCore;
using Microsoft.Azure.WebPubSub.Common;
using System.Text.Json;
using Azure.Core;

// Corrected server side code for chatting via hub
sealed class Hub : WebPubSubHub
{
    private readonly WebPubSubServiceClient<Hub> _serviceClient;

    public Hub(WebPubSubServiceClient<Hub> serviceClient)
    {
        _serviceClient = serviceClient;
    }

    public override Task OnConnectedAsync(ConnectedEventRequest request)
    {
        Console.WriteLine($"[SYSTEM] {request.ConnectionContext.UserId} joined.");
        return Task.CompletedTask;
    }

    public override async ValueTask<UserEventResponse> OnMessageReceivedAsync(UserEventRequest request, CancellationToken cancellationToken)
    {
        // Create message data
        var messageData = new
        {
            from = request.ConnectionContext.UserId,
            message = request.Data.ToString()
        };

        // Convert to JSON
        var json = JsonSerializer.Serialize(messageData);

        // Use the simplest overload of SendToAllAsync
        await _serviceClient.SendToAllAsync(json);

        return new UserEventResponse();
    }
}

Program.cs

using Microsoft.AspNetCore.Builder;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Azure.WebPubSub.AspNetCore;
using Microsoft.Azure.WebPubSub.Common;
using Azure.Core; // Add this using directive for RequestContent and ContentType
using Microsoft.Extensions.Primitives; // Add this using directive for StringValues

var builder = WebApplication.CreateBuilder(args);

// Add services to the container
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();
builder.Services.AddControllers();
builder.Services.AddCors(options =>
{
    options.AddPolicy("AllowAll",
        builder =>
        {
            builder.AllowAnyOrigin()
                   .AllowAnyMethod()
                   .AllowAnyHeader();
        });
});

// Load configuration from appsettings.Development.json
builder.Configuration.AddJsonFile("appsettings.Development.json", optional: true, reloadOnChange: true);

// Retrieve connection string
string connectionString = builder.Configuration["WebPubSubConnectionString"]
?? throw new InvalidOperationException("WebPubSubConnectionString is not configured.");

// Read connection string from environment
if (connectionString == null)
{
    throw new ArgumentNullException(nameof(connectionString));
}

builder.Services.AddWebPubSub(o =>
{
    o.ServiceEndpoint = new WebPubSubServiceEndpoint(connectionString);
})
.AddWebPubSubServiceClient<Hub>(); // Explicitly set the hub name


var app = builder.Build();

// Map Web PubSub endpoint
app.UseRouting();

// Configure the HTTP request pipeline
if (app.Environment.IsDevelopment())
{
    app.UseSwagger();
    app.UseSwaggerUI();
    //app.UseDeveloperExceptionPage();
}
else
{
    app.UseExceptionHandler("/Home/Error");
    app.UseHsts();
}

app.UseRouting();

app.UseCors("AllowAll");

// Map a Web PubSub hub to an API endpoint in server to communicate
app.MapWebPubSubHub<Hub>("/eventhandler");

app.MapControllers();

app.Run();

My Hub class name is 'Hub' and pubsub's hub name is 'socketio' and per documentation these 2 need not be same, it needs mapping socketio hub <----> Hub.cs which is done.
Tried keeping same name also but no difference.

JS client code:

Index.html

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Azure Web PubSub Minimal Client</title>
    <script src="https://cdn.jsdelivr.net/npm/socket.io-client@4.5.4/dist/socket.io.min.js"></script>
  </head>
  <body>
    <script>
      // Function to connect to Azure Web PubSub
      async function connectToWebPubSub() {
        try {
          const response = await fetch(
            "http://localhost:5000/api/v1/pubsub/negotiate"
          );
          if (!response.ok) {
            console.error(
              "Failed to negotiate, status code =",
              response.status
            );
            return;
          }

          const data = await response.json();
          console.log("Negotiated WebSocket URL:", data.url);

          // Extract path from negotiated URL
          const url = new URL(data.url);
          const socket = io(url.origin, {
            path: url.pathname, // Use path from negotiated URL
            transports: ["websocket"],
            pingInterval: 55000,
            extraHeaders: {
              "Sec-WebSocket-Protocol": "json.webpubsub.azure.v1",
            },
          });

          socket.on("connect", () => {
            console.log("Connected successfully!");
          });

          socket.on("message", (msg) => {
            console.log("Message from server:", msg);
          });

          socket.on("connect_error", (err) => {
            console.error("Connection error:", err);
          });

          // Send a message to the server
          socket.emit("howdy", "stranger");
        } catch (error) {
          console.error("Error connecting to Web PubSub:", error);
        }
      }

      window.onload = connectToWebPubSub;
    </script>
  </body>
</html>

So if you place these files in an empty API project, it should run for you.

Issue: I will be having multiple hubs for multiple purpose like chatHub, mediaHub so I guess it is important to establish a socket connection between client and pubsub via sockets for real time conversation and map pubsub hubs to related .cs classes and override methods in c#.net.

Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-22T20:06:29.0366667+00:00

Checking your code. Thank you for your response.
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-25T03:31:32.04+00:00

In the existing default mode, all Socket.IO clients connect directly to Azure Web PubSub. developers don't need to worry about if they have 100 or 1 million concurrent users. The service handles scaling up or down to meet the fluctuation of application users.
Devender Singh 25 Reputation points

2025-03-25T04:14:02.0566667+00:00

I understand that, code fixes pls!
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-26T09:24:42.3+00:00

I understand your concern regarding maintaining user-group connections between the client and server while using Azure Web PubSub for Socket.IO. However, there is an important architectural difference to consider.

In Web PubSub’s Socket.IO mode, clients communicate directly through Web PubSub, and the .NET server does not sit in the middle of message transmission like a standard Socket.IO setup. This means that expecting user-group session management between client and server is not feasible in this setup.

I see you are adding user management in your code, which is not present for PubSub Socket.IO, unlike using only Azure PubSub that supports groups and users. My code, as shared above, connects to both the client and server.
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-27T20:27:56.6233333+00:00

Hello Devender Singh Have you checked the comment?
Devender Singh 25 Reputation points

2025-03-28T03:21:27.2166667+00:00

Hi @sampath

lets say we might not have feature to map individual class to hubs in socketio pubsub. But atleast we can send messages from client to server through pubsubSocketio via websockets? Bcs in your shared implementation I see you are making http post call to send messages from client to server, which is not inline with the concept of pubsub.

If we can resolve that and directly send msgs from clients via sockets through pubsub it will be helpful.

Thanks
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-28T04:54:10.5933333+00:00

Hello @Devender Singh Are you thinking of using axios.get?
/
const response = await fetch( "http://localhost:5000/api/v1/pubsub/negotiate" );

Please let me know.
Devender Singh 25 Reputation points

2025-03-29T06:20:19.05+00:00

Hi @Sampath

either axios or native fetch api it is going to be https I guess. I am looking for a way to send my messages via socket connection from client. Pls let me know if this part is included in your shared code. Or how can we achieve this since we are using pubsub for sockets only than http.
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-04-01T04:27:59.95+00:00

Hello Devender Singh Could you please check the private chart and respond there?

1 answer

Your answer

Prabhavathi Manchala 2,315 Reputation points Microsoft External Staff Moderator

2025-03-18T06:33:06.65+00:00

Hi Devender Singh,

The error happens because the path in the generated client access URL does not match the audience expected by Azure Web PubSub for Socket.IO.

var uri = _webPubSubServiceClient.GetClientAccessUri(userId: "Dev"); var url = uri.AbsoluteUri.Replace("https://", "").Replace("/client/hubs/socketio", "/clients/socketio/hubs/socketio:443"); return Ok(new { url });

Make sure you are using the latest version of the Azure.Messaging.WebPubSub SDK. If you are using an older version, update it through NuGet as below.

dotnet add package Azure.Messaging.WebPubSub --version latest

Ensure cross the configuration of your WebPubSub resource in Azure. Ensure that the hub name (socketio) is correctly mapped and that it expects connections in the correct format.

Please try to manually construct the URL as shown below.

wss://azurepubsubforsocketio.webpubsub.azure.com/clients/socketio/hubs/socketio/access_token=<....>

Kindly refer below document for Client Endpoint and Client Path.

https://learn.microsoft.com/en-us/azure/azure-web-pubsub/socketio-quickstart#write-client-code

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Prabhavathi Manchala 2,315 Reputation points Microsoft External Staff Moderator

2025-03-20T00:50:55.8066667+00:00

Hi Devender Singh,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Devender Singh 25 Reputation points

2025-03-20T03:37:23.0733333+00:00

Hi Prabhavathi Manchala

PFB

error CS1061: 'WebPubSubServiceClient' does not contain a definition for 'GenerateClientAccessToken'

and still getting below trace:

Failed invoking 'tunnel:/eventhandler/' for 'hub:socketio,event:connect,type:sys,category:connections,requestType:Connect'. ClientRequestId: 'ddec0c2c-0cfa-47c7-b68a-627af1907c69'.

Looking for 'how to setup pubsub and server' connection in .net for socketio pubsub
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-22T10:36:19.1366667+00:00

Hello @Devender Singh ,have you checked the above comment?
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-22T20:06:29.0366667+00:00

Checking your code. Thank you for your response.
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-25T03:31:32.04+00:00

In the existing default mode, all Socket.IO clients connect directly to Azure Web PubSub. developers don't need to worry about if they have 100 or 1 million concurrent users. The service handles scaling up or down to meet the fluctuation of application users.
Devender Singh 25 Reputation points

2025-03-25T04:14:02.0566667+00:00

I understand that, code fixes pls!
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-26T09:24:42.3+00:00

I understand your concern regarding maintaining user-group connections between the client and server while using Azure Web PubSub for Socket.IO. However, there is an important architectural difference to consider.

In Web PubSub’s Socket.IO mode, clients communicate directly through Web PubSub, and the .NET server does not sit in the middle of message transmission like a standard Socket.IO setup. This means that expecting user-group session management between client and server is not feasible in this setup.

I see you are adding user management in your code, which is not present for PubSub Socket.IO, unlike using only Azure PubSub that supports groups and users. My code, as shared above, connects to both the client and server.
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-27T20:27:56.6233333+00:00

Hello Devender Singh Have you checked the comment?
Devender Singh 25 Reputation points

2025-03-28T03:21:27.2166667+00:00

Hi @sampath

lets say we might not have feature to map individual class to hubs in socketio pubsub. But atleast we can send messages from client to server through pubsubSocketio via websockets? Bcs in your shared implementation I see you are making http post call to send messages from client to server, which is not inline with the concept of pubsub.

If we can resolve that and directly send msgs from clients via sockets through pubsub it will be helpful.

Thanks
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-28T04:54:10.5933333+00:00

Hello @Devender Singh Are you thinking of using axios.get?
/
const response = await fetch( "http://localhost:5000/api/v1/pubsub/negotiate" );

Please let me know.
Devender Singh 25 Reputation points

2025-03-29T06:20:19.05+00:00

Hi @Sampath

either axios or native fetch api it is going to be https I guess. I am looking for a way to send my messages via socket connection from client. Pls let me know if this part is included in your shared code. Or how can we achieve this since we are using pubsub for sockets only than http.
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-04-01T04:27:59.95+00:00

Hello Devender Singh Could you please check the private chart and respond there?

Answer 1

@Devender Singh

Update- For C#, the team is actively working on releasing a new SDK version that will support Socket.IO as a request type. While progress is being made, we’re currently unable to provide a fixed ETA.

For Node.js, the @azure/web-pubsub 1.1.4 already supports Socket.IO through the WebPubSubClientProtocol type in the getClientAccessToken() method.

You can refer to the documentation here: https://learn.microsoft.com/en-us/javascript/api/%40azure/web-pubsub/webpubsubclientprotocol?view=azure-node-latest

Share via

Negotiated url is not working while connecting to Azure webpubsub for socketio

1 answer

Your answer