Integration with Business (On-prem) (also known as Anaconda Server)#
Anaconda Navigator comes with everything you need to seamlessly integrate to your instance of Anaconda Server, our Business (On-prem) tier offering. You can set up the Anaconda Server API domain, log in with credentials, add channels, and install/update packages from Anaconda Server with Anaconda Navigator.
Log in action#
To integrate with Anaconda Server:
Click Connect in the top-right corner of the Navigator application.
Click Sign In next to Anaconda Server. You can only be signed into one repository service at a time.
If this is the first time you are logging in to Anaconda’s Business tier, you’ll be asked to set your Anaconda Server domain.
Enter your domain and click Set Domain.
If your domain is correct, you’ll see the login dialog.
Enter the credentials you use to log in to your Anaconda Server instance.
Click Login. If all credentials are correct, you will be signed in.
Add default channels action#
After signing in, a dialog appears with a list of available channels. You can choose what channels to use and what channels to add to default_channels by clicking on the checkboxes in the Add to default_channels and Add to channels columns. After you’ve marked channels, click on Add Channels. This step can be skipped by clicking Skip.
CLI Login Detection#
If you have already logged in using CLI, Navigator will detected that and you’ll be asked to check your channels configuration. See Add default channels action for further instruction.
A few things happen “under the hood” when you successfully log in:
Your access token is created for Anaconda Server. This provides you with the ability to access private/authenticated/public channels, create environments, and download packages.
anaconda_server_token_idin the Navigator config file (anaconda-navigator.ini) are updated. This is mostly system data to help Navigator integrate with the Anaconda Server.
The token and token ID config variable names have been updated from
anaconda_server_token_idas of Version 2.4.0. If you downgrade your Navigator application to a version older than 2.3.0, you will need to manually change these variable names back to their older versions within your
The access token is stored locally, which gives conda ‘native’ access to remote channels and packages.
Once signed in, you will be able to add private channels in the
Manage Channels dialog using the
<my_channel_name> format, rather than
Click Update Index to gain access to all packages located in private/authenticated/public channels in the Anaconda Server instance.
A few things happen “under the hood” when you successfully log out:
The conda configuration file (
.condarc) returns to the state it was in before the login. (Navigator saves a copy of the
.condarcfile before a login in attempted.)
anaconda_server_token_idare set to
Nonein the Navigator config file (
The access token created in the Anaconda Server instance is removed.
The access token that was stored locally is removed.
Change Anaconda Server API domain#
To set the Anaconda Server API domain, go to the navigation bar and click on Preferences. In Anaconda Server API domain, enter the valid domain name:
Alternatively, this API domain can be set through the Configure Navigator action:
Click Configure Navigator to open your
anaconda_server_api_urlparameter under the
[main]section of the
anaconda-navigator.inifile and enter your domain name (by default, the value is set to
The domain must be a full path without a trailing slash. For example:
Click Save and Restart to apply your changes.
If you are having issues logging in or know you’re logged in but cannot interact with Anaconda Server, see Trouble logging in to the Anaconda Server connection in Navigator.