Pesquisas recentes
Sem pesquisas recentes

Alex Leventis
Entrou em 07 de fev. de 2024
·
Última atividade em 07 de fev. de 2024
Seguindo
0
Seguidores
0
Atividade total
2
Votos
0
Assinatura
1
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Alex Leventis
Alex Leventis comentou,
We are working through Enabling JWT single sign-on migration.
When a user is authenticated, they are successfully logged into the app via the "return_to" param which in our case is https://support.{domain}.com
When we receive the /access/unauthenticated response, the browser auto-redirects back to our sign-on page. Which is essentially the same as clicking "sign-in", bringing the user back to our remote login URL.
However, we have no way of knowing if the zendesk authentication failed upon rendering our sign-on page.
Because we can only submit this POST request as form data, we cannot capture the returned url after the request is made.
As of now, this introduces a loop in our system. Here are network details
Can you please prevent the automatic redirection from https://support.bitly.com/access/unauthenticated to our remote login url. But instead redirect to the return_url (a url query param on the unauthenticated response), or display an auth error, or provide insight on how to handle this situation?
I've looked through the admin console's single sign on settings, but there are not configuration changes we can make on our end.
Exibir comentário · Editado 07 de fev. de 2024 · Alex Leventis
0
Seguidores
0
Votos
0
Comentários