Guardian-push restricting me from editing app config

[matt.howell]

The free tier plan we are demoing is encountering the same problem.

Auth0 Dashboard, Auth0 Deploy CLI(if you are using it) or both?

Dashboard

disable the Cross-Origin Authentication option for your application?

Already disabled

do you have the Client Initiated Backchannel Authentication (CIBA) enabled by any chance?

Do not see the setting

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

Not using CLI

[char-bone]

Removing the async_approval_notification_channels property worked for us. We didn’t add this ourselves. It seems it gets added to the config somehow when exporting even though it’s disabled in the ui.

[alberto.leal]

I just found this option in my app settings… client-initiated backchannen authetication on

turned off guardion push option and solved the issue…..

after turning off, I can not see this option anymore

[nik.baleca]

Hi everyone!

I am sorry about the discomfort and issues caused by the error above in your tenants preventing to save the configuration.

For more information related to the error, it appears to be caused by the new Client Initiated Back Channel Authentication feature. This flag appears to be generated automatically for new applications if it is enabled on the tenant, however, in the case of users in this topic, it appears to have been migrated to preexisting applications. Otherwise, this feature is still in Early Access.

As I have mentioned previously and other users confirmed this, the solution would be to remove the "async_approval_notification_channels": ["guardian-push"] field by setting it to null.

This can be done in the following ways:

• Via the Dashboard under the application’s settings. You should see a section titled Client-Initiated Backchannel Authentication (CIBA) where you will be able to turn off the guardian-push option
• If the section above does not appear, check you application’s grants by going to Advanced → Grant Types → Client Initiated Backchannel Authentication and enable/disable it and check if the section mentioned above appears.
• Disable it from the Auth0 Management API by setting the value to null. The body should be:

{
"async_approval_notification_channels": null
}

• If you are using Terraform or Deploy CLI, removing the flag or setting it again to null inside the respective yaml/tf files.

This should do the trick in getting rid of the error and be able to modify your application’s configuration.

Kind Regards,
Nik