Neil Murphy

Working off of this document:

https://developer.zendesk.com/documentation/classic-web-widget-sdks/support-sdk/working-with-the-support-sdk/building-a-dedicated-jwt-endpoint-for-the-support-sdk/#json-web-token-response

It's not clear, but the endpoint that receives the `user_token` needs to be url-form-encoded rather than JSON. Could you please update that doc so that it's explicit?

Is all of this equally applicable to Mobile SDK integration, as well as SSO integration?

Is it the case that only the “optional properties” listed above are supported? The Mobile SDK integration tutorial indicates that “everything else is optional,” and we'd like to stuff additional custom properties at the payload's top level.