You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I am using the auth0 cli to update the prompt texts for login-id, however when I run:
auth0 branding texts update -l en login-id
I see the following error message:
!! Uh oh. Something went wrong.
!! If this problem keeps happening feel free to report an issue at
!!
!! https://github.com/auth0/auth0-cli/issues/new/choose
If I run auth0 branding texts update -l en login
I am able to change the text for the login prompts, however I am using the identifier first login page so I believe I need to edit login-id texts.
Thank you for your help and let me know if I can provide more info!
Expectation
Expect auth0 branding texts update -l en login-id to open an editor to edit the prompt texts.
Reproduction
Given I am logged into my auth0 tenant
When I run auth0 branding texts update -l en login-id
@daschi – Thanks for submitting this issue, it certainly appears to be frustrating. I'm currently in the middle of troubleshooting this and have determined that it's a duplicate of #515. For that reason, I'm opting to close this ticket and communicate all status updates in the other ticket. Thank you for your patience!
Checklist
Description
Hello! I am using the auth0 cli to update the prompt texts for
login-id
, however when I run:auth0 branding texts update -l en login-id
I see the following error message:
If I run
auth0 branding texts update -l en login
I am able to change the text for the login prompts, however I am using the identifier first login page so I believe I need to edit
login-id
texts.Thank you for your help and let me know if I can provide more info!
Expectation
Expect
auth0 branding texts update -l en login-id
to open an editor to edit the prompt texts.Reproduction
auth0 branding texts update -l en login-id
Auth0 CLI version
auth0 version 0.13.1 42a703d
The text was updated successfully, but these errors were encountered: