Sam

Hello Greg Katechis

The problem does not come from our LdP.

The problem comes from the connection url generated by Zendesk. 
For example, on this page: 
https://mywebsite.zendesk/hc/fr/requests/new?ticket_form_id=123456789&tf_subject=lorem%20ipsum

the connection url generated by Zendesk will be: "/hc/fr/signin?return_to=https%3A%2F%2Fmywebsite.zendesk.com%2Fhc%2Ffr%2Frequests%2Fnew%3Fticket_form_id%3D123456789"
The parameter "tf_subject" is not present. 

Testing with an unknown parameter, like lorem_param=lorem ipsum, the parameter is well preserved. 
For example, on this page: https://mywebsite.zendesk/hc/fr/requests/new?ticket_form_id=123456789&lorem_param=lorem%20ipsum
the connection url generated by Zendesk will be : 
"/hc/fr/signin?return_to=https%3A%2F%2Fassistance.leboncoin.info%2Fhc%2Ffr%2Frequests%2Fnew%3Florem_param%3Dlorem%2520ipsum%26ticket_form_id%3D123456789"

Can you check why Zendesk does not generate a connection link with all the tf_ parameters?

 

Hello, 

We have enable the single sign-on connection, via JWT token.
When we access to a form with a prefilled ticket form, (like tf_123456=lopsem), if end user is already connected, it's working well. 

However, if end user is not connected, after connection and redirect to the form url, the prefilled ticket form parameter disappeared from the form url 
Exemple of workflow :

1.  Access to https://mywebsite.zendesk.com/hc/fr/requests/new?ticket_form_id=123456789&tf_987654321=lorem ipsum (end user not connected)
2. Redirect to http://mywebsite.com/login (user connect)
3. Automaticly redirect to https://mywebsite.zendesk.com/hc/fr/requests/new?ticket_form_id=123456789 (tf_987654321 is lost)

How can we keep tf_ parameter when end user is redirected after connection ?