Alexa Skill will no longer authenticate to link
-
The Alexa skill no longer authenticates with the username and the password that works with the monoclecam portal. It appears that “linking” the skill is no longer possible.
-
@vmsman I have the same issue
-
@ALL.
Sorry, about the delay in getting this issue resolved. I was away from my office all last week and unable to access the necessary details and resources to work on this problem.
PLEASE TRY AGAIN NOW. (You may need to restart your Monocle Gateway instances.)
The issue started when I replaced all the SSL certificates at the end of January. Even though we have a pre-paid and valid 5 year certificate, the SSL rules require that it gets replaced annually now. So after updating all the certificates and restarting all the services that allow Monocle to function, it all appeared to be working from my local testing. However somewhere in the changes … the Monocle/Alexa authentication service failed to re-connect to the Monocle backend database properly. Perhaps it was holding onto (cached) the previous SSL for its secure connection which then expired. I’ll have to dig a bit deeper to better understand why it continued to fail to connect over the course of several days, but I believe this was the underlying issue causing failed account re-linking, failure to refresh Alexa tokens and failure for Monocle Gateway to reconnect and throw 401 errors.
Please let me know if any of you have further issues getting Monocle working again.
Thanks, Robert
