Support Multiple Connection Strings (with Different EntityPaths) in a Shared Azure Service Bus Namespace

[WillemCoudron]

We would like to use Wolverine with Azure Service Bus in a multi-tenant SaaS architecture.

• We have one shared Service Bus namespace.
• Each client has their own topic, represented by an EntityPath.
• For security reasons, each client uses a different set of credentials / SAS policies, scoped only to their own entity.

In our current setup (previously with MassTransit), we publish to each client’s topic using a unique connection string, even though all the entities are in the same namespace.

Each client has access only to their own topic, which is needed for tenant isolation.

To the best of our knowledge, Wolverine does not seem to support multiple connection strings with EntityPath. As a result, if we try this, we seem to get unauthorized errors using client-specific topics (with limited SAS credentials and EntityPath in the connection string).

We would like to request for Wolverine to support multiple Azure Service Bus publishing connections, even if they use the same namespace.

[jeremydmiller]

@WillemCoudron We have this for Rabbit, Amazon SQS, and Kafka. Haven't done it for Azure Service Bus because nobody has asked for that until now. There's plenty of prior art now if you'd like to try to tackle that in a PR. Honestly more work to set up test cases for it than to actually code it.

I can certainly talk w/ you about a JasperFx engagement to deliver it quickly if you'd like.

[WillemCoudron]

@jeremydmiller Thank you for your response!
My colleague has sent you an email regarding a potential JasperFx engagement, but we’re not sure if the email address (Yahoo) is still used. If that’s not the best way to reach you, could you please let us know your preferred way to contact you?
Thank you in advance!

Hey @WillemCoudron, sorry, try jeremy@jasperfx.net. That old yahoo account is active, but it's 25 years old (gulp) and super spammed!

[jeremydmiller]

Hey @WillemCoudron, sorry, try jeremy@jasperfx.net. That old yahoo account is active, but it's 25 years old (gulp) and super spammed!d for expected response

WEIRD, I didn't even know you could edit other people's comments on GitHub. I'll probably try to sell you on just grabbing a support contract and we'll just embed this feature in for you.

[KrzychuR]

I'm also interested in how I could help. Could you provide some guidance on where to start before I begin analyzing the code step by step?

[jeremydmiller]

@KrzychuR Sorry I missed this. Look for the AddNamedKafkaBroker() code and see how that was done.

And follow this PR maybe: #1589

Should be some rinse and repeat. Only issue is that ASB is annoying in testing because you have to actually have a real ASB namespace going.

[WillemCoudron]

@jeremydmiller we have implemented the feature and are testing it on our own codebase.

2 things:

• We can't seem to figure out the testing structure, so we haven't been able to create those
• We don't have write permissions, so we can't push the branch and create a PR

[jeremydmiller]

@WillemCoudron "We don't have write permissions, so we can't push the branch and create a PR" ? Why can't you push a pull request?

For testing, you'd have to have a second namespace. I think w/ Rabbit MQ I used the Envelope.Destination to verify it all went to the right place.

I guess in the absence of anything other better options, you can still export a patch file with git and send that here somehow.

[KrzychuR]

@WillemCoudron I can help with testing if needed, still limited time for coding around it :(

[WillemCoudron]

@KrzychuR I created a pull request with the added feature: #1762. Let me know if any more changes are needed.