Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to use acli rovodev without sudo. Error: failed to store authentication configuration

Tomasz Małecki
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2025

Hi. 

Installed acli on my MacOS using homebrew

brew tap atlassian/homebrew-acli
brew install acli
acli --version
I am unable to auth using `acli rovodev auth login` using my email and token. 

In result - I authed using `sudo acli rovodev auth login` and that's the only way CLI now works. 

There is no logs from login procedure that I can share. 

2 comments

Comment

Log in or Sign up to comment
Christian Langeveld
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2025

Did you do:

sudo mv ./acli /usr/local/bin/acli
sudo chown root: /usr/local/bin/acli

Like Jovana Dunisijevic likes this
Jovana Dunisijevic
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 4, 2025

Hey @Tomasz Małecki 

Thank you for sharing these details!

This issue is often related to file permissions when installing ACLI via Homebrew on macOS. If you need to use sudo for authentication and running the CLI, it usually means the configuration or credential files were created with root ownership, so your regular user can't access them.

 

To fix it, try this:

  1. Try resetting the permissions on the ACLI config directory:

    sudo chown -R $(whoami) ~/.acli ~/.rovodev

    This will ensure your user owns the config and credential files.

  2. After that, try running acli rovodev auth login again (without sudo).

  3. If you still have issues, try uninstalling and reinstalling ACLI as your regular user (not with sudo), and repeat the login process.

Why this happens:

  • Running acli with sudo creates config files as root, which blocks normal user access.

  • Homebrew installs should not require sudo for running CLI tools.

If you continue to have trouble, please let us know the exact error message or behaviour you see after fixing permissions. 

Kindest regards,

Jovana

TAGS
AUG Leaders

Atlassian Community Events