Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

64-bit browser is scrubbing out ltpatoken from cookie

  • 2 respostas
  • 1 tem este problema
  • 1 visualização
  • Última resposta por astuer

astuer
astuer
more options

when trying to login to a server configured for single sign-on, all works well using a 32-bit browser, the server responds with the ltpatoken and the browser correctly re-uses the received ltpatoken in it's next requests to the server. BUT when using a 64-bit browser, on the same workstation, connecting to the same server, the browser suddenly scrubbs out the ltpatoken from the cookie which breaks the flow and the user cannot open the web application as blocked on the login prompt.

Has anyone an idea what can cause this strange behavior. My browser settings are standard, I didn't change anything. But could it be that 64-bit has some strickter security setting which makes the browser think the ltpatoken in the cookie isn't correct ? we don't have the security bit set on the token, the domain accompanying the token is correct, so not sure what else to check as all works fine switching to 32-bit browser !

when trying to login to a server configured for single sign-on, all works well using a 32-bit browser, the server responds with the ltpatoken and the browser correctly re-uses the received ltpatoken in it's next requests to the server. BUT when using a 64-bit browser, on the same workstation, connecting to the same server, the browser suddenly scrubbs out the ltpatoken from the cookie which breaks the flow and the user cannot open the web application as blocked on the login prompt. Has anyone an idea what can cause this strange behavior. My browser settings are standard, I didn't change anything. But could it be that 64-bit has some strickter security setting which makes the browser think the ltpatoken in the cookie isn't correct ? we don't have the security bit set on the token, the domain accompanying the token is correct, so not sure what else to check as all works fine switching to 32-bit browser !

Solução escolhida

I finally found the cause of this issue. Security has been enforced on 64-bit browsers and additionally in Windows10. The following RFC 6265 was implemented (which isn't implemented in 32-bit browsers and not generally on windows7 workstations) which includes a check on the cookie attribute "Domain" against the public domain suffix list (https://publicsuffix.org/list/public_suffix_list.dat). I my case the token domain was included in this list which caused the browser to reject the cookie. After modifying the token dns domain to a value not included in the public domain list, the problem was solved !

Ler esta resposta no contexto 👍 0

Todas as respostas (2)

Pj
Pj
more options

astuer said

When using a 64-bit browser, on the same workstation, connecting to the same server, the browser suddenly scrubbs out the ltpatoken from the cookie which breaks the flow and the user cannot open the web application as blocked on the login prompt...

I'll guess at this. What about turning OFF Content Blocking or reducing the Blocking? (My settings, attached. Try other setups.)


~Pj

astuer
astuer Proprietário da pergunta
more options

Solução escolhida

I finally found the cause of this issue. Security has been enforced on 64-bit browsers and additionally in Windows10. The following RFC 6265 was implemented (which isn't implemented in 32-bit browsers and not generally on windows7 workstations) which includes a check on the cookie attribute "Domain" against the public domain suffix list (https://publicsuffix.org/list/public_suffix_list.dat). I my case the token domain was included in this list which caused the browser to reject the cookie. After modifying the token dns domain to a value not included in the public domain list, the problem was solved !