Azure web pub sub CheckPermissionsAsync call throws 404

Jumwal, Karan Motilal 46

Before granting a permission to group, I am checking if the user connection already has that permission. The CheckPermissionAsync method returns 404 (Head).

VenkateshDodda-MSFT 23,141 Reputation points Microsoft Employee

2024-05-16T07:40:24.41+00:00

@Jumwal, Karan Motilal Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Could you please help us with the documentation steps that you are following and also more details what exactly you are trying to do?

So that I can check with the internal team and update you accordingly.
Jumwal, Karan Motilal 46 Reputation points

2024-05-16T08:17:27.69+00:00

@VenkateshDodda-MSFT

We are using Azure web pub sub for we socket live connection. We have custom authorization code which authorizes users and grant send message to group permission to the user connection. Before granting this permission, I check if the user connection already has that permission. To this I call CheckPermissionAsync method which does a Head request as below:

HEAD /api/hubs/NotificationStore_Hub/permissions/joinLeaveGroup/connections/OVuUL23XfkZgmjlY87WUcQHkrJUQn02

We are getting 404 status code as response for above request.

Accepted answer

Siyuan 75 Reputation points Microsoft Employee

2024-05-16T10:06:52.7366667+00:00
Hi @Jumwal, Karan Motilal , 404 is one of the expected response codes of this API according to our API Doc. It could be caused by either of cases below:

The given ConnectionId doesn't exist. The response message should be like "Connection <connection-id> is not found."

The given ConnectionId exists but it doesn't have the target permission. The response message should be like "Connection <connection-id> doesn't have the permission joinLeaveGroup"
Please sign in to rate this answer.
Jumwal, Karan Motilal 46 Reputation points

2024-05-16T12:32:14.1466667+00:00

Thanks @Siyuan Xing

Jumwal, Karan Motilal 46 Reputation points

2024-06-12T09:48:30.96+00:00

Hello @siyuan Xing

We are assigning the permission to connection id using pub sub sdk at server side which makes below PUT call:
/api/hubs/NotificationStore_Hub/permissions/joinLeaveGroup/connections/OVuUL23XfkZgmjlY87WUcQHkrJUQn02

What is better approach and will perform better from below?

Check if permission exists and if not exists then assign.

Assign it without checking and let pub sub service handle it in the background.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure web pub sub CheckPermissionsAsync call throws 404

0 additional answers

Your answer