SachinG.26887 (Customer) asked a question.
Hello,
After configuring a brand new integration with the newer Integrator tenant - https://integrator-3146120.okta.com, I’m encountering an issue. The “The page has timed out. If this page does not reload automatically, please refresh your browser.” message is displayed only when executing the test automation script.
However, if I log in manually, the issue doesn’t occur. I’ve checked the System reports and rate limits, but there are no apparent issues.
Could you please advise on any settings that need to be updated for the automation script to continue functioning? I’ve never encountered this issue with the older Dev tenants.
I’ve added the code to refresh the page three times if this issue occurs, but adding the logic to auto-refresh the page doesn’t resolve the issue either.
Please let me know if any further information is required
@SachinG.26887 (Customer) is this behaviour consistent across the browsers? Which application have you integrated?
I see that you are trying to access okta dashboard.
Was this behaviour same from the 1st login after you got the integrator tenant created?
Hello Rohit, we test only the Chrome browser. I have integrated the Hypr Application https://www.okta.com/integrations/hypr/
Is there any settings that I need to update, please let me know.
I attempted to use my two colleagues’ tenants, one of which was a trial account and the other an integrator, to determine if this issue was specific to my tenant. However, I encountered the same error with both of those tenants as well. Is Okta implementing some sort of rate limit configuration that is blocking traffic? Are there any settings that I need to update to resolve this problem? Please let me know.
Hypr link shared supports inbound federation setup to okta.
The setup might be incorrect. Have you configured IDP in okta and have the metadata exchanged?
Do you see any logs in okta
Reports> System logs
Set up is all good on my end. As I mentioned in my original post, the issue doesn’t happen when I log in manually. However, the Okta timeout error only occurs when the test automation script runs on a build machine without an external monitor attached.
I’ve attached screenshots of the system log of the automation run and rate limits for your reference.
@RohitU.50441 (Trevonix) any suggestions please?