為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Error Logging Into APEX Applications When Redirected to Login - Firefox 57.0.x

  • 2 回覆
  • 3 有這個問題
  • 1 次檢視
  • 最近回覆由 WestEnd

more options

When using Firefox 57.0.x we are experiencing an issue logging into LDAP authenticated Oracle APEX applications. The problem occurs when using a friendly URL to direct to an APEX application login page, it does not occur if the full-length APEX application URL is used to access the app. The issue causes the first login attempt to fail (producing the error: ORA-01403: no data found). Proceeding login attempts are successful if the browser tab is left open. Because of this, clients are needing to login twice every time they want to use an APEX application with Firefox 57.0.x. This issue does not occur with Chrome or IE, nor does it occur with Firefox 56.0.x. The APEX applications that have this Firefox 57.0.x login issue use LDAP authentication schema, our applications that use APEX authentication schema are not affected by this problem.

When using Firefox 57.0.x we are experiencing an issue logging into LDAP authenticated Oracle APEX applications. The problem occurs when using a friendly URL to direct to an APEX application login page, it does not occur if the full-length APEX application URL is used to access the app. The issue causes the first login attempt to fail (producing the error: ORA-01403: no data found). Proceeding login attempts are successful if the browser tab is left open. Because of this, clients are needing to login twice every time they want to use an APEX application with Firefox 57.0.x. This issue does not occur with Chrome or IE, nor does it occur with Firefox 56.0.x. The APEX applications that have this Firefox 57.0.x login issue use LDAP authentication schema, our applications that use APEX authentication schema are not affected by this problem.
附加的畫面擷圖

所有回覆 (2)

more options

Our workaround for this issue was to direct our friendly URLs to a new intermediary APEX app landing page with full-length APEX URL links for users to click. Accessing the APEX apps using the full-length URLs resolves the login issue, so the addition of the landing page allows users to continue to use the friendly URLs and then click a link on the landing page for app access. However, this does add an additional step for users.

The original issue still remains. If there are any known solutions or better workarounds, posted replies would be appreciated.

more options

AFAIK the institution that I work at uses APEX as well but we are told to use IE to access APEX because of the integration with the software that they use that FF and Chrome doesn't properly open APEX.