Did you add the token you generated in azure, to the connector? I usually try to establish the connection using an easier tool first, like Postman or SOAP UI. After successfully creating that connection I apply the same configuration to the client that I am configuring. Some screenshots of the connector and/or postman/SOAP UI would be helpful especially if you can establish the connection elsewhere.
Are you refering to the “AMQP workflow trigger” or the “azure service bus” block credentials ?
Because I understand help of postman (or similar) for getting the oauth2 authentication for the “azure service bus” block but not for the ampq trigger one ?
I wasn’t the one who generated the token unfortunately. But I used the token generated in Azure. If my memory is correct, when generating the token you need to set permissions for that token. If the permissions are set correctly you should be able to call it using a simpler interface. I was following this method because it is really difficult to detect the actual problem when there is one and its even more difficult if there is more.
I would check Access Control settings for token first and then test it using something simpler.
Hey, no we are trying on purpose to use the “AMPQ workflow trigger” rather the “azure service bus” connector one. (as mentioned in my initial message, including capture of the AMQP connecteur settings panel)
Why:
Azure Service Bus is compatible with AMQP protocol (which is a standard. source)
We want to trigger workflow when messages on specific queue or subscriber are received. (can’t make this with the standard azure service bus connector except if linked with a clock trigger: buy buy event driven)
we have already a tenant and a contract with microsoft azure, including protection of our data (GDPR and stuff).
Note: We are currently supporting AMQP 0-9-1 messaging protocol.
I found in Wikipedia page, it’s indicated that Azure SB and RabbitMQ are implemented using different version of the AMQP protocol. You can refer here too: AMQP 0-9-1 Protocol Specification — RabbitMQ
Apache Qpidmaintains support for multiple AMQP versions
RabbitMQ, an open-sourceproject sponsored by VMware, primarily supports AMQP 0-9-1, with 1.0 via a plugin
Because of this, the AMQP connector won’t be able to connect to AZ SB and there could be error that was not showing in the UI while configuring the account.
To workaround this issue and since there is no trigger for Azure Service Bus connector, you may want to consider implementing a clock trigger with the frequency you want and then utilize MS Azure Service Bus connector to pull the data in.
