Guardian-push restricting me from editing app config

Get Help
,
1

I didn’t turn on MFA configuration. Somehow when i change CORS configuration, it keeps the following error:

Error!
Please upgrade your subscription to use the async approval notification channels: guardian-push

how do i solve it?

6 Likes
2

I have same issue when I try to change callback url, it stared today I think

1 Like
3

I’m just trying to change my logout URL and I’m getting the same error. I’ve confirmed that all MFA settings are disabled in my tenant.

1 Like
4

same. Trying to update callback URLs

6

Hi everyone!

I will investigate the issue and come back with an update ASAP! Thanks for letting us know about the issue that you are experiencing!

By any chance, do any of you have any actions bounded which would enforce guardian MFA?

Kind Regards,
Nik

7

I’m using one post login action that does not to my knowledge enforce guardian MFA. It makes a call out to my server to check for pending invitations and potentially sets the user app metadata.

8

We’ve encountered the same issue. We do have enterprise plan.

1 Like
9

We are also seeing this issue.

10

Running into the same problem when trying to update the callback URI on an existing SPA. Any updates?

11

I am also having this issue which is preventing me from saving any changes to my Application in the Dashboard.
I have never touched any of these features, and this issue seems to have begun now that my free trial period has ended (today). This continues even after manually going to the “Multi-factor Auth” page and clicking Save with everything (already) disabled there.

12

We are also having this issue on any application or machine created Nov 8th. (network panel shows 403) when any edit is made, haven’t been able to submit a ticket from the support center either (might be related)

13

Same issue happening here. Also, like others, I cannot submit a support ticket about the issue.

14

This issue is preventing us from deploying an update for a customer that is due tomorrow. An update on potential resolution would be greatly appreciated.

15

Hi everyone,

Just for further confirmation regarding the issue, are you receiving the aforementioned error when trying to update an application only in the Auth0 Dashboard, Auth0 Deploy CLI(if you are using it) or both?

Additionally, are you able to save the tenant configuration if you disable the Cross-Origin Authentication option for your application?

For the applications that you cannot configure, do you have the Client Initiated Backchannel Authentication (CIBA) enabled by any chance?

If you are using Deploy CLI, does your application configuration include the following flag:

async_approval_notification_channels: - guardian-push

If this flag is included in your configuration, I would recommend disabling/removing it, let me know if that changes anything regarding the matter.

Kind Regards,
Nik

16

Hi Nik,

All we did is try to rename our app name under Auth0 Dashboard and receiving the following error:
Error!Please upgrade your subscription to use the async approval notification channels: guardian-push

17

I’m in the Auth0 Dashboard, trying to save my Single Page Application. I do not currently have ‘Allow Cross-Origin Authentication’ enabled. If I load the Settings page and click Save with making no changes, I even receive the error.

18

using the CLI worked after removing the async_approval_notification_channels entries.

19

I can confirm that I am also randomly receiving this error today when simply trying to rename an application:

Error!
Please upgrade your subscription to use the async approval notification channels: guardian-push

I have not to my knowledge ever knowingly or intentionally enabled guardian-push on anything, it simply broke today when it was previously working.

EDIT: Further to this…

I had created all of the affected applications through the web interface some time ago, not using the API/CLI.

If I now query the applications through https://TENANT.REGION.auth0.com/api/v2/clients I can see that they all contain the following:

 "async_approval_notification_channels": [
            "guardian-push"
],

This is despite never configuring them (in fact in many cases, the applications are pretty much completely default, i.e. I clicked Create and then Next/Finish, without further configuring them).

If I now create a new application, it does not contain this async_approval_notification_channels section.

So I can only assume that something behind the scenes has modified these already existing applications to add this guardian-push to them.

Question:
Can these applications be fixed through the UI to remove this config (which I did not add), or do I need to try and patch them all through the API to remove this?

EDIT2:

If I update the application through the API as follows, I am then able to edit the application through the web UI again as before:

PATCH https://TENANT.REGION.auth0.com/api/v2/clients/CLIENT_ID

Body: {"async_approval_notification_channels": null}

I’d like to re-iterate though, that I did not do anything to enable this in the first place.

7 Likes
20

Hi everyone, @leigh.gordon @nik.baleca I am trying to update the Auth0 setting by using Management API, but it returned me the 401 invalid token issue every time even I already used the latest token from Management API. Do you know what happen with Auth0 today?

21

I have a fresh account updated to a paid plan today, can’t update any of my apps for the same reason. Turned it on and off in the security tab but no luck