Recherches récentes
Pas de recherche récente

David Gilman
Adhésion le 10 févr. 2025
·
Dernière activité le 10 févr. 2025
Suivis
0
Abonnés
0
Activité totale
1
Votes
0
Abonnements
0
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par David Gilman
David Gilman a créé une publication,
I have the messaging widget configured with the login callback that provides it with a JWT. The JWT is valid: I can see in the web console that the messaging widget makes a call to a `/login` route with that JWT and that route returns HTTP 200 with the correct details for the user that was described in the JWT.
However, even after all that happens, the messaging widget still goes through the “What is your name?” and “What is your email?” questionnaire as if the user did not have JWT authentication at all. The resulting ticket created by the messaging widget in Zendesk itself is one for a non-authenticated user.
Is there anything else I can double check to investigate this? From what I can tell I'm providing the right JWT to the chat widget and the chat was able to partially use it. I also opened a ticket to Zendesk support but it's been a week with no response.
Publication le 10 févr. 2025 · David Gilman
0
Abonnés
1
vote
1
Commentaire