You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I build a BOT using the "webex-node-bot-framework" and it works fine with my private account. I change the bot key to the bot I created for the corporate space and the framework starts up OK. Websocket connections are OK. But when the first message is sent to the bot, the app panics with the error "Hostname of 1st certificate does not match 'kid'" - I don't understand why this happens. What are the differences between using websocket in "public" or "corporate" spaces? Can a company use other certificates? Isn't the websocket connection established only to the Webex network? How can I fix this without security issues?
Thanks, Alex
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I build a BOT using the "webex-node-bot-framework" and it works fine with my private account. I change the bot key to the bot I created for the corporate space and the framework starts up OK. Websocket connections are OK. But when the first message is sent to the bot, the app panics with the error "Hostname of 1st certificate does not match 'kid'" - I don't understand why this happens. What are the differences between using websocket in "public" or "corporate" spaces? Can a company use other certificates? Isn't the websocket connection established only to the Webex network? How can I fix this without security issues?
Thanks, Alex
Beta Was this translation helpful? Give feedback.
All reactions