Authentication issue when trying to process orders

[rkralston]

I have everything set up. I run the order generator. I can see the messages hitting the queue. Nothing happens in AKS.

When I look at the k8s tool in Code, the order-processor has a red dot next to it. I'm not sure what to do from there.

I noticed in the YAML that it is pulling the image from your Docker account?

Should I package that in a new container and deploy the image to my ACR?

[rkralston]

I created the local docker image and ran it as in the src readme. When I look at the logs, they show failures:
[10:11:54]fail: Keda.Samples.Dotnet.OrderProcessor.OrdersQueueProcessor[0] Unable to process message Microsoft.Azure.ServiceBus.UnauthorizedException: Put token failed. status-code: 401, status-description: ExpiredToken: The token is expired. Expiration time: '2019-08-27 11:11:54Z'.

[tomkerkhove]

The service bus connection string does not seem to be valid anymore, can you verify that?

[rkralston]

The generator is not having an issue creating messages with that connection string.

I've created 604 messages that I can't remove.

[tomkerkhove]

The generator uses send permissions while the message pump uses receive permission. So that is not a guarantee, can you pleasure generate a new one with these permissions please?

[rkralston]

Getting the same result with new key.

[tomkerkhove]

Are you sure that the generated base64 representation is correct? (ie no trailing spaces)

The error clearly indicates that it's an authentication issue when trying to start processing the messages

[rkralston]

I'm copying it using the portal copy function.

I've tried to stand the Processor up locally, from the command line, outside Docker. I can't get that to run. I keep getting JSON error.

[tomkerkhove]

Are you creating the subscription on the queue itself or the namespace? I presume you've verified that you have Receive/Manage permissions?

Does it work in Service Bus Explorer?

[rkralston]

On the queue.

Not sure what you mean by verify. I looked at both subscriptions and they both have manage.

I'll try service bus explorer tomorrow.

[tomkerkhove]

Hi @rkralston, did you manage to test this? If so, did you get it working?

[rkralston]

No. We abandoned KEDA b/c it is considered experimental by MS.

[tomkerkhove]

That's fair. For what it's worth, that might change soon.

[rkralston]

Please let me know if it does.i am very excited about keda. I think it is a total game changer. If I had bandwidth, this would be my open source project of choice. Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: Tom Kerkhove <[email protected]> Sent: Monday, November 4, 2019 5:29:00 PM To: kedacore/sample-dotnet-worker-servicebus-queue <[email protected]> Cc: Keith Ralston <[email protected]>; Mention <[email protected]> Subject: Re: [kedacore/sample-dotnet-worker-servicebus-queue] Authentication issue when trying to process orders (#8) That's fair. For what it's worth, that might change soon. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#8?email_source=notifications&email_token=AAHZELFH47EL2DP5SEI7PGDQSCV3ZA5CNFSM4IQJOC4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDBCLEQ#issuecomment-549594514>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHZELHFT2B7WQ3UPCMZZD3QSCV3ZANCNFSM4IQJOC4A>.

[jakobehn]

Keda went GA back in november, and is ready for production usage:
https://cloudblogs.microsoft.com/opensource/2019/11/19/keda-1-0-release-kubernetes-based-event-driven-autoscaling/

[jakobehn]

For what it's worth, I had this exact error when running a Docker container on my local machine that (at the time) had an incorrect system time. Clock mismatch makes the SAS token validation go nuts. After manually setting the correct time on my host, the problem went away

[johnknoop]

I'm getting this despite having the correct time on my docker host 😕

Edit: restarting the host solved the problem.

[tomkerkhove]

Good to hear and sorry for the issues, unfortunately there's not much I can do about it..

[crgarcia12]

I just had the same situation. Restarting docker worked