# Allow other methods of whitelisting Bot Detection for Production E2E tests **URL:** \ **Category:** Product Feedback\ **Created:** [October 27, 2025, 6:23pm UTC](https://community.auth0.com/t/allow-other-methods-of-whitelisting-bot-detection-for-production-e2e-tests/193701 "2025-10-27T18:23:33Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![shauli.bracha](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/shauli.bracha/32/72644_2.png) [@shauli.bracha](https://community.auth0.com/u/shauli.bracha)\ **Post date:** [October 27, 2025, 6:23pm UTC](https://community.auth0.com/t/allow-other-methods-of-whitelisting-bot-detection-for-production-e2e-tests/193701/1 "2025-10-27T18:23:33Z")
**Feature:** Allow other methods of whitelisting Bot Detection for E2E tests **Description:** Bot detection whitelisting is by IP address only. When running e2e tests on ephemeral machines (such as github actions) with no static IP, Auth0 detects the Playwright bot and presents a captcha. Allowing more methods of whitelisting could help. **Use-case:** Running E2E tests on Production. We can’t enable the `password` grant type as it’s not recommended. We have to sign in via the UI. In these cases the bot detection is triggered, showing a captcha and the tests fail. ---
**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\ **Post date:** [October 31, 2025, 8:32pm UTC](https://community.auth0.com/t/allow-other-methods-of-whitelisting-bot-detection-for-production-e2e-tests/193701/2 "2025-10-31T20:32:36Z")
Hi there! Welcome to the Auth0 Community! Thank you for creating this feedback card. Please make sure to upvote it so that it gets as many votes as possible and attracts as many community members as possible. Thanks Dawid