Búsquedas recientes
No hay búsquedas recientes

Mikhail Nikitin
Incorporación 01 dic 2021
·
Última actividad 08 dic 2021
Seguimientos
0
Seguidores
0
Actividad total
3
Votos
0
Suscripción
1
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Mikhail Nikitin
Mikhail Nikitin hizo un comentario,
Thank you!
Would like to receive additional clarification regarding the information provided previously.
Will user email addresses be used by Zendesk beyond the process of uniquely identifying a user? If so, could you please specify how exactly? To send email notifications or be relayed to some internal or external services for any kind of processing, maybe? Will GDPR-compliance be maintained in any such case?
It would be preferable for us to identify users by external IDs instead of email addresses since in most cases MobileSDK is the channel used by our users to submit requests. I understand, however, that email address is required.
Ver comentario · Editado 08 dic 2021 · Mikhail Nikitin
0
Seguidores
0
Votos
0
Comentarios
Mikhail Nikitin creó una publicación,
We’re in the process of implementing JWT-authentication for one of our apps instead of Anonymous authentication. We're using native support SDK for Android/iOS.
‘JWT Claims set’ of a JWT request should contain an email address, which, according to the respective article, is used as the unique identifier for a user unless an external ID is received.
It appears that “Email” is not an optional field, and a claims set should contain some email for a user to be identified.
Is it possible to use a placeholder email address instead of the one provided by a user with JWT authentication for it to work? Question is also brought up by GDPR-related concerns.
Please advise.
We're using the following documentation.
Publicado 01 dic 2021 · Mikhail Nikitin
1
Seguidor
2
Votos
3
Comentarios