We’re trying to use a custom template for our universal login. We created a custom domain, but when I run auth0 universal-login templates update, I get an error config.json file is missing.
I understand you have experienced an error when trying to update your Universal Login page template.
After my investigation, I was not able to reproduce the same errors as you when using the Auth0 CLI.
When trying to call auth0 universal-login templates update, I got the unknown command "universal-login" for "auth0" error message.
From my experience, the config.json file is only needed for the Auth0 Deploy CLI and not the Auth0 CLI. Typically, you would make a request that would look something like the following:
One thing that confuses me is that the documentation says to use the auth0 branding command, but the Auth0 CLI tool doesn’t have that command (I’m referencing commands listed under “Available Commands”), and instead has auth0 universal-login. Do you know what’s going on?
Alright, it looks like the error went away with time (maybe it was a propagation thing), as today I’m able to use auth0 universal-login templates update to update the custom template, but the update doesn’t look like it’s been applied. The Auth0 documentation has a reference to “update the code” to use the custom domain for the Universal Login, but I don’t know where that would be. Any thoughts?
So, just to recap, I believe the main issue from this post ( “config.json file is missing”) is just resolved with time, but @ skirasirov, please add your experience!
I also figured out my second issue. We needed to update the URL that we point to in our app from the original domain to our custom domain.