Manage Azure Relay from dotnet core 3.1 with shared access policy
See original GitHub issueQuery/Question Is it possible to manage Azure Relay with a shared access policy connection string with Manage claim on dotnet core 3.1?
Environment:
- Name and version of the Library package used: Microsoft.Azure.Management.Relay 2.0.2
- Hosting platform or OS and .NET runtime version: Microsoft.AspNetCore.App 3.1.9
- IDE and version : Visual Studio 16.7.7
I’m upgrading relay management code from classic service bus management library WindowsAzure.ServiceBus to the new relay management library. Previously we issued a shared access secret based on a policy that included Manage claim and configured our existing app with a service bus connection string. Using the classic full framework library we could manage WCF relays, even in a new Azure Relay namespace.
I’ve tried acquiring a token using Microsoft.Azure.Relay.TokenProvider.CreateSharedAccessSignatureTokenProvider(keyName, key) but this token is of course a SharedAccessSignature token intended for the service bus namespace endpoint and not Azure Resource Manager.
Is there a similar library like the service bus Microsoft.Azure.ServiceBus.Management.ManagementClient(connectionString)
that can be used to manage Azure Relay on dotnet standard?
My reason for asking is that we have legacy code that we don’t want to issue certificates and create app registrations for to be able to acquire token from AAD. This legacy code should also be restricted to only manage service bus and relay resources.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top GitHub Comments
@joaroyen, we should be getting back to you soon. Thanks for your question.
Thanks for the response. Not exactly what we wanted to hear, and I believe we will distribute certificate and use the Microsoft.Azure.Management.Relay library.