You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use an Azure Relay to do some local web service testing. This is using a modified HybridConnectionReverseProxy from the examples. The modification is to use some of the Azure.Identity features (similar to ManagedIdentity) as a TokenProvider. I have a wrapper that will use any TokenCredential, such as DefaultAzureCredential. It's effectively the same implementation as the ManagedIdentityTokenProvider. I can successfully retrieve a token, but the listener.OpenAsync call gets an exception WebSocketException: The server returned status code '500' when status code '101' was expected..
It seems like this type of token isn't supported. We're trying to move away from secrets, so support for this would be very helpful.
The text was updated successfully, but these errors were encountered:
I'm trying to use an Azure Relay to do some local web service testing. This is using a modified
HybridConnectionReverseProxy
from the examples. The modification is to use some of the Azure.Identity features (similar to ManagedIdentity) as aTokenProvider
. I have a wrapper that will use anyTokenCredential
, such asDefaultAzureCredential
. It's effectively the same implementation as theManagedIdentityTokenProvider
. I can successfully retrieve a token, but thelistener.OpenAsync
call gets an exceptionWebSocketException: The server returned status code '500' when status code '101' was expected.
.It seems like this type of token isn't supported. We're trying to move away from secrets, so support for this would be very helpful.
The text was updated successfully, but these errors were encountered: