# Cookie issue causing infinite loop during login attempt with Firefox, but not Chrome **URL:** \ **Category:** OAuth/OIDC\ **Created:** [September 16, 2022, 2:27pm UTC](https://devforum.okta.com/t/cookie-issue-causing-infinite-loop-during-login-attempt-with-firefox-but-not-chrome/21903 "2022-09-16T14:27:10Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![efinch](https://avatars.discourse-cdn.com/v4/letter/e/b3f665/32.png) [@efinch](https://devforum.okta.com/u/efinch)\ **Post date:** [September 16, 2022, 2:27pm UTC](https://devforum.okta.com/t/cookie-issue-causing-infinite-loop-during-login-attempt-with-firefox-but-not-chrome/21903/1 "2022-09-16T14:27:10Z")
Our application can log in successfully against Okta with Chrome, but when the user is on Firefox, the process turns into an infinite loop, bouncing back and forth between Okta and our website. If the user goes into the Firefox browser settings and puts the Okta url into the Cookie exception list with the Allow flag, then login works. What setting do we need to change, server side, to allow the login process to work, without forcing users to make this local setting change? Can this be accomplished by making a change in the Okta server settings, or do we need to handle it separately from each application? Thank you. ---
**Author:** ![alexedwards.ac](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@alexedwards.ac](https://devforum.okta.com/u/alexedwards.ac)\ **Post date:** [September 5, 2023, 4:02pm UTC](https://devforum.okta.com/t/cookie-issue-causing-infinite-loop-during-login-attempt-with-firefox-but-not-chrome/21903/2 "2023-09-05T16:02:22Z")
We’re having the same issue. any luck on your end? ---
**Author:** ![efinch](https://avatars.discourse-cdn.com/v4/letter/e/b3f665/32.png) [@efinch](https://devforum.okta.com/u/efinch)\ **Post date:** [September 5, 2023, 6:21pm UTC](https://devforum.okta.com/t/cookie-issue-causing-infinite-loop-during-login-attempt-with-firefox-but-not-chrome/21903/3 "2023-09-05T18:21:42Z")
I still don’t have a solution beyond telling users to make the change in their browser settings, which is really unacceptable. ---
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [February 13, 2024, 12:58am UTC](https://devforum.okta.com/t/cookie-issue-causing-infinite-loop-during-login-attempt-with-firefox-but-not-chrome/21903/4 "2024-02-13T00:58:15Z")