Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPIKE] Okta user keeps getting locked out for Cypress E2E tests #8320

Open
mpbrown opened this issue Nov 25, 2024 · 2 comments
Open

[SPIKE] Okta user keeps getting locked out for Cypress E2E tests #8320

mpbrown opened this issue Nov 25, 2024 · 2 comments
Assignees

Comments

@mpbrown
Copy link
Collaborator

mpbrown commented Nov 25, 2024

Description

Our Cypress E2E tests use a test account named Cypress McTestUser in the Okta lower environment. The logs show that this account is used successfully for a period of time, but then begins to fail the stage of "Authentication of user via MFA" due to "INVALID_CREDENTIALS". These failures continue until Okta locks the account which results in all E2E test runs failing. The account must then be manually unlocked via the Okta admin panel.

Separately, this test account uses an email of a developer no longer working on SimpleReport.

See this Slack thread for a short overview of the logs

Proposed Solutions

  • Investigate what may be causing the failed authentication
  • Possibly retire Cypress McTestUser and create a new account with fresh credentials
@mpbrown mpbrown changed the title Okta user keeps getting locked out for Cypress E2E tests [SPIKE] Okta user keeps getting locked out for Cypress E2E tests Nov 26, 2024
@mpbrown mpbrown added the sync label Dec 2, 2024
@DavidMcClatchey DavidMcClatchey self-assigned this Dec 9, 2024
@DavidMcClatchey
Copy link
Collaborator

Rate limit for username/password validation is 4 per second per user, so that doesn't seem likely to be the issue.

Similarly for tokens, the rate limit seems to be above what would cause this.

@DavidMcClatchey
Copy link
Collaborator

Created a new Cypress test user account [email protected]. This may or may not resolve the issue, but it at least gives us more control over it as compared to using an account from someone who's no longer on SimpleReport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants