Hello Victor,
thank you for taking this case. Essentially what I am trying to do is replace Kerberos right, so I would like to be able to connect to Solace from the console app and do publish/ subscribe with OAuth. At this moment I am manually setting some JWT token from Azure which is a valid token. On the side of Solace, I am not really sure if I understand the concept of Client or Resource Server, but I have configured the resource server OAuth profile, based on the fields JWT token I pretty set the required AUD to match in the Solace (in parse token section) and hit save.
I can see in the Stats tab that the requests are coming but it fails on the invalid token part, so maybe you can point me in the right direction maybe how to get some logs on why it is invalid in my .NET console I have set debug logging, but it really does not say anything about the token and also if you are able to clarify the difference between the Client and the resource server would be very valuable, since, for example, I do have Client Secret, Client Id from the registered app in Azure, but that is not really in the token, so does it mean that if I provide it, that the solace would act as a client which can ask the Azure for the token itself? If so, how can I leverage that from the .NET console?
Thank you for your help.
Kind regards,
Stan.