Fail to decrypt conversation id about botframework-services

[sbuffkin]

Just double checking, this is a plain old bot right off the template correct, echo bot or basic bot? Which sdk are you using? (v3/v4 nodejs/c#)?

[sbuffkin]

Also, it would probably be a good idea to open up this issue on the actual repo for your SDK:

nodejs
C#

[ricardopieper]

@nyxsys i'm using the Bot Channels Registration, not using any templates. We're calling the Directline API methods ourselves.

I created this issue to get more info on what this error actually means. "Failed to decrypt conversation id" doesn't tell me what I'm doing wrong. Maybe I messed up some credentials in my application, but the error should tell me what it actually happened.

I just redid everything from scratch again and it worked. Re-created the whole resource on Azure and everything. If I see this error again I can point the application ID and everything else.

[ricardopieper]

Also, "doesn't tell me what I'm doing wrong" is a common theme for us and Microsoft lately.

I assume I'm messing stuff up, but the error responses aren't helping even a bit. #1 is an example of that.

[JasonSowers]

@ricardopieper you are calling the directline methods via the rest API?

[ricardopieper]

@JasonSowers yes, we are. This problem stopped happening after I recreated everything from scratch, so that might have been a mistake on my end.

However, I found the "fail to decrypt conversation id" a bit weird, seems like that's an error message only useful for the Bot Framework backend, and not for the end user of the API.

To give credit where it's due, @ksikorsk found out that I was using the wrong conversation ID in the URL in an unrelated issue (#1). This mistake was fixed today, and I feel like it could cause this issue somehow.

I'll let you guys decide if this issue should be closed, for me it's no problem, I can reopen if this happens again.

[dandriscoll]

@ricardopieper thanks for providing detail on this issue. We started independent verification a few days ago that confirms this issue is specific to the skypeforbusiness channel. We have your other issue tracking the 400 and ErrorResponse object so given that we've identified the source, I'm closing this issue now.