ArtA.53613 (Customer) asked a question.
I am trying to setup an inline hook for the telephony interface. I am receiving the request from Okta, and I'm sending back the following JSON response, but I keep getting the error message "Could not deserialize inline hook response due to error at Line 1 Column 2" when previewing the hook request/response:
{
"commands": [
{
"type": "com.okta.telephony.action",
"value": [
{
"status": "SUCCESSFUL",
"provider": "ClickSend",
"transactionId": "e4fa35f8-5bf0-4e75-a46e-82f1649ca39e"
}
]
}
]
}
I've also tried sending it back without pretty-printing, like so:
{"commands":[{"type":"com.okta.telephony.action","value":[{"status":"SUCCESSFUL","provider":"ClickSend","transactionId":"e4fa35f8-5bf0-4e75-a46e-82f1649ca39e"}]}]}
But it still does not work. I keep getting the error.
Any idea what is wrong?
Hi, @ArtA.53613 (Customer)
Thank you for posting on our Community page!
Here is a helpful article on your use case:
https://support.okta.com/help/s/article/token-inline-hook-execution-failed-could-not-deserialize-inline-hook-response?language=en_US
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Yes, I saw that article. As you can see in my previous post, the JSON is formatted correctly. So I don't think that is the problem.
My only other thought is that when I test in postman, it works. Postman has a feature turned on to follow redirects. I discovered that since I am using a Google App Script for the go-between, Google returns a 307 redirect as a security precaution whenever it returns JSON data. If Okta is reading the response from the 307 instead of following the redirect, that may be the problem. Can someone confirm that? I found another Okta article that said they had trouble with event hooks and redirects, too.