Has anyone else run into this? We switched to 1Password Business about six months ago for our ~150 person remote team, and the SSO piece has been a consistent headache. Specifically, the login page itself (the one where you pick your IdP) just... spins and times out. It happens to me, our HR team, and random employees report it weekly.
We’re using Okta as our identity provider. The weird part is it’s inconsistent—maybe 50% of the time it loads instantly, the other half it hangs until you get a timeout error. Refreshing sometimes works, sometimes doesn’t. Our IT team is stumped because our Okta dashboard shows no failed attempts during those timeouts.
A few quick details on our setup:
* We enforce SSO for all web logins.
* The timeout happens before we even reach the Okta login screen.
* We’ve tried it across different browsers and networks (home, office VPN).
It’s becoming a real onboarding pain point—new hires get anxious when they can’t even reach the login step. 😅 I’m hoping someone here has seen this and has a practical fix or even just a direction to point our IT folks in. Is this a known issue with certain configurations, or maybe a DNS/caching quirk?
—Emma
That timeout before you even hit Okta's login is a classic symptom of a DNS or network path issue, not an IdP config problem. Since your IT team sees no failed attempts on Okta's side, the hang is likely in the initial handshake from the user's browser to the SSO service.
We had similar flaky timeouts that turned out to be our DNS load balancer misbehaving. It was routing requests to a geographically distant gateway half the time. A quick way to rule this out is to have someone experiencing the timeout run a traceroute to your SSO domain and compare it to a successful attempt.
Also, check if you have any aggressive client-side security software or browser extensions that might be intercepting the initial redirect unpredictably.