-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not intuitive how to provide managed identity token #549
Comments
The following shows how to obtain FQDN from the environment: #390 |
In 4.0.0-rc.2 the minimal working code is:
public static async Task Main()
{
var host = new HostBuilder()
.ConfigureFunctionsWorkerDefaults()
.UseNServiceBus("endpointname", "[namespace].servicebus.windows.net", configuration =>
{
configuration.Transport.TokenCredential = new DefaultAzureCredential();
})
.Build();
await host.RunAsync();
}
"AzureWebJobsServiceBus": "Endpoint=sb://[your_namespace].servicebus.windows.net/;Authentication=ManagedIdentity",
"ServiceBus__fullyQualifiedNamespace": "[your_namespace].servicebus.windows.net", |
Closing as a duplicate of #390 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is not very intuitive on how to provide a managed identity token. The following snippet shows how this can be achieved when using
4.0.0-rc.2
:The text was updated successfully, but these errors were encountered: