Doesn't validate certificate for incoming request (according to Cert team)

I’m using your library for my Alexa skill (great job on it btw!)

For the past several months, I’ve been working with the cert team to get my skill approved (this frustration is a topic for another day though). Through January, they would come back with requested changes to the behavior of the skill.

Since around mid-Feburary, Amazon has started rejected my attempts because they say that The skill does not validate the certificates for the incoming requests and is accepting requests with incorrect certificate. Please refer to the document that describes how to build your Alexa Skill as a web service I racked my brain about what I could have changed and finally blew away my full library and updated it again from virgin source (i.e, I’ve made no changes to it).

Again, I received a rejection saying the same thing. Has anyone else noticed this? Could Amazon have changed their process and made it incompatible with the current library per chance?

Finally, how would I go about testing this piece - is there a way to get Amazon to send me a bogus request that I can debug against?

[smoore4moma]

One thing to watch out for is web.config. Most of us were taught to hide errors from users, so it is common to redirect ANY error to an error page, like this:

<customErrors mode="On" defaultRedirect="~/Home/Error" />

I changed this to <customErrors mode="Off" /> and that worked. Not a AreYouFreeBusy app but might be relevant anyway.

[stefann42]

@rosariomartone please open a new issue since what you are asking is unrelated to this particular issue. In short, you are using the library incorrectly. VerifyCertificateUrl is an internal function not meant to be called by you (should have probably been marked private). There is no need to you to perform certificate validation explicitly. It’s something the library does implicitly.