SignalR Trigger supports base64 encoded claims

[Y-Sindo]

Library name

Microsoft.Azure.WebJobs.Extensions.SignalRService

Please describe the feature.

Currently SignalR serverless protocol uses a format like "a: v, b: v" to represent users' claims, which causes some problems including but not limited to:

1. Claim values are truncated at first comma  #27225
2. Multiple jwt claims of the same type not supported? azure-functions-signalrservice-extension#260, Only one claim of type 'role' is returned to the hub azure-signalr#1084

To solve these problems, we intend to add a new header X-ASRS-User-Claims-Encoded to hold the base64 encoded claims. The fix requires both an ASRS runtime change and SignalR Functions extension change.

• ASRS runtime change
• SignalR Functions extension change

[github-actions]

Hi @Y-Sindo, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.