-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent Login is ignored on MacOS #1306
Comments
The configuration file
The Commander is expected to be installed in its own Python virtual environment. |
I am not sharing the The pip install is done using pipx so it does have it's own venv. |
Do you use the same account on your MacOS and Linux boxes?
|
I do use the same account on both machines. I managed to get the python package installed, I needed to install Persistent login is still an issue, however, here is the output of my
I still cannot run more than one command without having to authenticate every time. |
Is it possible that
|
The file is not read-only, but is only writable by my local user. |
The Commander needs to be able to write to this file |
I am running commander under the same user |
The Commander team is not aware of any persistent login issue when it stops working with no reason. The Commander updates |
I am using Commander (16.11.15 installed via PKG) on MacOS 14.5 with an M2 CPU. I have Persistent Login set and my device timeout is 14 days, however, I am prompted to perform SSO authentication after every command.
I have a second machine running Ubuntu 24.04 and Commander 16.11.14 (installed via pip) that does not exhibit the same behavior and seems to respect the device timeout.
I am also unable to install Commander via pip on the Mac as it runs into dependency issues with libav.
Please let me know what additional information I can provide.
The text was updated successfully, but these errors were encountered: