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

[IAMRISK-3539] Use signup captcha enforcement endpoint for signup flow #2586

Closed
wants to merge 4 commits into from

Conversation

TSLarson
Copy link
Contributor

@TSLarson TSLarson commented Oct 2, 2024

Changes

This PR separates the bot detection enforcement policy from login and signup. When the signup screen is selected, the bot detection enforcement policy is now selected from the NEW signup endpoint.

References

https://auth0team.atlassian.net/browse/IAMRISK-4032

Testing

  • This change adds unit test coverage
  • This change adds integration test coverage
  • This change has been tested on the latest version of the platform/language

Checklist

@TSLarson TSLarson requested a review from a team as a code owner October 2, 2024 14:22
"auth0-password-policies": "^1.0.2",
"blueimp-md5": "^2.19.0",
"classnames": "^2.3.2",
"dompurify": "^2.3.12",
"dompurify": "^2.5.4",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated due to Snyk error in CI

src/core/remote_data.js Fixed Show fixed Hide fixed
// there is no id for the unselected tab (Login is selected by default)
const signUpTab = window.document['querySelector']('.auth0-lock-tabs > li:nth-child(2) > a');
Simulate.click(signUpTab, {});
}

Check notice

Code scanning / CodeQL

Semicolon insertion Note test

Avoid automated semicolon insertion (98% of all statements in
the enclosing script
have an explicit semicolon).
@TSLarson TSLarson closed this Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants