Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

Firefox 40 breaks our web app

  • 2 ответа
  • 3 имеют эту проблему
  • 2 просмотра
  • Последний ответ от jcavallaro

more options

Our web app breaks with the upgrade to FF v40. On one of the pages the user can click on a button that will run a report in a modal-popup window. The report is pulled from our reporting server (RePortal) and is a Crystal Report. The user prior to v40 was prompted for their AD credentials to run the report. Now FF does not prompt for the AD credentials of the user and just throws a 401 Error saying that the user is not Authorized...of course their not they didn't log in yet. Downgrading to 39 and everything works again.

Not every user has access to certain report data.

The temporary work around is to open a FF tab and log directly into the RePortal server then go back to our web app and run the report.

HELPPPPPP!!!!!

Все ответы (2)

more options

Выбранное решение

more options

jcavallaro said

Our web app breaks with the upgrade to FF v40. On one of the pages the user can click on a button that will run a report in a modal-popup window. The report is pulled from our reporting server (RePortal) and is a Crystal Report. The user prior to v40 was prompted for their AD credentials to run the report. Now FF does not prompt for the AD credentials of the user and just throws a 401 Error saying that the user is not Authorized...of course their not they didn't log in yet. Downgrading to 39 and everything works again. Not every user has access to certain report data. The temporary work around is to open a FF tab and log directly into the RePortal server then go back to our web app and run the report. HELPPPPPP!!!!!

Thanks Phillip...not really the answer I was hoping for. Can the site it is being redirected be trusted and allow for the change of origin. https to https on the same domain is not the problem. The problem in my case is two different hosts. One is the application server the other is the reporting server.