# Allow allowRememberBrowser in challengeWith and challengeWithAny API

**URL:** <https://community.auth0.com/t/allow-allowrememberbrowser-in-challengewith-and-challengewithany-api/194457>\
**Category:** Product Feedback\
**Tags:** actions, api\
**Created:** [November 13, 2025, 7:18pm UTC](https://community.auth0.com/t/allow-allowrememberbrowser-in-challengewith-and-challengewithany-api/194457 "2025-11-13T19:18:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![b.boone](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/b.boone/32/61001_2.png) [@b.boone](https://community.auth0.com/u/b.boone)\
**Post date:** [November 13, 2025, 7:18pm UTC](https://community.auth0.com/t/allow-allowrememberbrowser-in-challengewith-and-challengewithany-api/194457/1 "2025-11-13T19:18:23Z")

</div>

**Feature:** Allow `allowRememberBrowser` in the`challengeWith` and `challengeWithAny`APIs

**Description:** The newer [challengeWith](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-api-object#api-authentication-challengewith-factor%252C-options) and [challengeWithAny](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-api-object#api-authentication-challengewithany-factors) APIs allow for fully customizing the MFA experience except for disabling `allowRememberBrowser`. Currently this is available with the older`api.multifactor.enable(‘any’, { allowRememberBrowser: false });`method. This deficiency has prevented us from adopting the new API as our use-case requires us to disable the `allowRememberBrowser` feature.

**Use-case:** Custom MFA experience where the ability to “remember me” is controlled by the user’s organization. The parameters/conditions for “remembering” the user are also customized.

---

<div class="post-metadata">

**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:** [November 28, 2025, 7:02pm UTC](https://community.auth0.com/t/allow-allowrememberbrowser-in-challengewith-and-challengewithany-api/194457/3 "2025-11-28T19:02:38Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![sdsea](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sdsea/32/70795_2.png) [@sdsea](https://community.auth0.com/u/sdsea)\
**Post date:** [July 31, 2026, 6:03pm UTC](https://community.auth0.com/t/allow-allowrememberbrowser-in-challengewith-and-challengewithany-api/194457/4 "2026-07-31T18:03:42Z")

</div>

Reposting here from a different forum thread:

Commenting for future users:

Although using `api.authentication.challengeWith*` or `api.authentication.enrollWith*` does not permit setting `allowRememberBrowser`, the Auth0 docs claim:

```  
When you allow the user to skip MFA, a cookie is  
stored in the user’s browser. If the user has the cookie set but you  
still want to require MFA, you have two options:

- Set `allowRememberBrowser` to `false`
- Set `acr_values` to `http://schemas.openid.net/pape/policies/2007/06/multi-factor` when calling the `/authorize` endpoint.

```

Currently, Auth0 does not in fact honor `acr_values` for the purpose of forcing MFA / bypassing a remembered browser. They have confirmed this is a bug, and encouraged sharing this with the Auth0 Community so they can gauge user interest in fixing the bug.

So… talk to your sales rep?
