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
I use a single username but have multiple organizations.
In 1.14.1 it seems that the web browser is being used to authenticate then it drops you into the "last org in the list" and you can't really change that in an obvious fashion.
I use
anaconda login
anaconda whoami
with anaconda.org
Let me know if you need more info to recreate.
My workaround has been to use anaconda-client version 1.13
I'm sorry you're having trouble with our new login experience. Can you please provide a bit more information so I can understand better? Historically, one would log into anaconda.org via username and password on the terminal. This would (internally) create and store an access token locally (associated with the user), which is then accessed when making authenticated requests.
We are still doing that same token handling, however we have replaced the first step with a more modern oauth2 implementation.
Can you please help me to understand how the experience has changed when using organizations? We ourselves use these too, and generally for package upload to an organization. In that case, it is anaconda upload --user <org_name>. Was it possible in the past to log in with organization as the username?
I will also add, this change was released in anaconda-client 1.14.0. However, there was a delay in the server implementation change, so the rollout date of the behavior was after the client release.
We included an environment variable (ANACONDA_CLIENT_LEGACY_INTERACTIVE_LOGIN=1) that can be used as a temporary means of reverting the new behavior.
But, per my last comment, I'd definitely like to understand the use case more to ensure we didn't miss an edge case in this transition.
Activity
mattkram commentedon Mar 3, 2026
I'm sorry you're having trouble with our new login experience. Can you please provide a bit more information so I can understand better? Historically, one would log into anaconda.org via username and password on the terminal. This would (internally) create and store an access token locally (associated with the user), which is then accessed when making authenticated requests.
We are still doing that same token handling, however we have replaced the first step with a more modern oauth2 implementation.
Can you please help me to understand how the experience has changed when using organizations? We ourselves use these too, and generally for package upload to an organization. In that case, it is
anaconda upload --user <org_name>. Was it possible in the past to log in with organization as the username?mattkram commentedon Mar 3, 2026
I will also add, this change was released in
anaconda-client 1.14.0. However, there was a delay in the server implementation change, so the rollout date of the behavior was after the client release.We included an environment variable (
ANACONDA_CLIENT_LEGACY_INTERACTIVE_LOGIN=1) that can be used as a temporary means of reverting the new behavior.But, per my last comment, I'd definitely like to understand the use case more to ensure we didn't miss an edge case in this transition.
hmaarrfk commentedon Mar 16, 2026
sorry for my late reply. trying to find the time to try this again.
One of the challenges i'm facing at the moment is logging in from my remote machines.
I typically ssh into a more powerful machine, and login and upload from there. But now with anaconda client 1.14.1 i cannot do that.
I guess I'll have to wait until i build a smaller package again locally.