# Add a New Client Host ## Overview In the following example: * The default domain and realm are `S2.LOCAL` * The Key Distribution Center (KDC) server is on `10.1.0.5` * The Kerberos admin server is on `10.1.0.5` ## Install Kerberos Tools and Obtain a Ticket 1. Install the `krb5-user` tools. **Red Hat** ```shell sudo yum install krb5-user ``` **Debian** ```shell sudo apt install krb5-user ``` 2. Enter the domain that will be connected to the default Kerberos realm. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt95729d91a579ee8a/6a3330ef08a4ff3f249cbeab/kerberos-enter-realm-NR93S4.png) 3. Enter the Kerberos authentication server. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt788fe832c8bed07f/6a333045a20711475eb6d681/kerberos-enter-auth-servers-FxJngz.png) 4. Enter the administrative server. ![](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt2de3ddec20d40759/6a33304022bc51cc024246fc/kerberos-enter-admin-server-XcM66j.png) 5. The `[realms]` section in the `/etc/krb5.conf` file on this host will now resemble the following. ```yaml [realms] S2.LOCAL = { kdc = 10.1.0.5 admin_server = 10.1.0.5 default_domain = s2.local } ``` 6. Obtain a ticket for a user that exists in the cluster. ```shell kinit user1@S2.LOCAL ``` ```output Password for user1@S2.LOCAL: ``` ```shell klist ``` ```output Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: user1@S2.LOCAL Valid starting Expires Service principal 09/28/22 10:46:12 09/28/22 20:46:12 krbtgt/S2.LOCAL@S2.LOCAL renew until 09/29/22 10:46:08 ``` ## Connect to SingleStore ## Install SingleStore Client * *Red Hat Distribution* ## Online InstallationFor online installations where the target host can access the SingleStore YUM repository, perform the following steps.**Note**: These steps are also provided in the [self-managed deployment guides](https://docs.singlestore.com/db/v9.1/deploy.md).1) Add the SingleStore repository to your repository list. ```shell sudo yum-config-manager --add-repo https://release.memsql.com/production/rpm/x86_64/repodata/memsql.repo ``` 2) Verify that the SingleStore repo information is listed under `repolist`. ```shell sudo yum repolist ``` 3) Verify that the `which` package installed. This is used during the install process to identify the correct package type for your installation. ```shell rpm -q which ``` If `which` is not installed, it must be installed before proceeding. If you cannot install `which`, you will have to specify the correct package during the deployment phase covered in the respective deployment guide. ```shell sudo yum install -y which ``` 4) Install the SingleStore client. ```shell sudo yum install -y singlestore-client ```## Offline InstallationFor clusters that must be deployed in an environment without Internet access, download the SingleStore client package onto a host that can access the main deployment host.Copy the SingleStore client package onto the target host (typically the main deployment host when deploying SingleStore) and install the SingleStore client.```shell sudo rpm -ivh /tmp/singlestore-client--.x86_64.rpm ``` * *Debian Distribution* ## Online InstallationFor online installations where the target host can access the SingleStore APT repository, perform the following steps.**Note**: These steps are also provided in the [self-managed deployment guides](https://docs.singlestore.com/db/v9.1/deploy.md).1) SingleStore packages are signed to ensure integrity, so the GPG key needs to be added to this host. When done, verify that the SingleStore signing key has been added using `apt-key list`. ```shell wget -O - 'https://release.memsql.com/release-aug2018.gpg' 2>/dev/null | sudo apt-key add - && apt-key list ``` **Without using `apt-key`**: ```shell wget -q -O - 'https://release.memsql.com/release-aug2018.gpg' | sudo tee /etc/apt/trusted.gpg.d/memsql.asc 1>/dev/null ``` 2) Verify that `apt-transport-https` is installed. ```shell apt-cache policy apt-transport-https ``` If `apt-transport-https` is not installed, it must be installed before proceeding. ```shell user-shell sudo apt -y install apt-transport-https ``` 3) Add the SingleStore repository to retrieve its packages. ```shell echo "deb [arch=amd64] https://release.memsql.com/production/debian memsql main" | sudo tee /etc/apt/sources.list.d/memsql.list ``` 4) Install the SingleStore client. ```shell sudo apt update && sudo apt -y install singlestore-client ```## Offline InstallationFor clusters that must be deployed in an environment without Internet access, download the SingleStore client package onto a host that can access the main deployment host.Copy the SingleStore client package onto the target host (typically the main deployment host when deploying SingleStore) and install the SingleStore client.```shell sudo dpkg -i /tmp/singlestore-client___amd64.deb ``` * *Tarball* ## Download the SingleStore ClientDownload the SingleStore client tarball file onto a host that can access the main deployment host.## Transfer the SingleStore ClientTransfer the SingleStore client tarball file into a dedicated `singlestore` directory on the target host (typically the main deployment host when deploying SingleStore) that has been configured so that non-`sudo` users can access it, such as `/opt/singlestore`.## Unpack the SingleStore ClientUnpack the SingleStore client tarball file into the `singlestore` directory.```shell tar xzvf singlestore-client--.x86_64.tar.gz ```Using symbolic links (or "symlinks") can make using and upgrading the SingleStore client easier. Performing the following steps will allow the `singlestore` command to be run from anywhere on the filesystem, even after an upgrade by updating the symlink.1) Navigate to the directory that contains the unpacked SingleStore client tarball file and create a `singlestore-client` symlink that points to the SingleStore client directory. ```shell ln -s singlestore-client-- singlestore-client ``` 2) Verify that the symlink has been created. ```shell ls -l ``` ```output singlestore-client -> singlestore-client-1.0.6-c3803db03b ``` 3) Update the `PATH` environment variable with the path to the new `singlestore-client` directory. This path can also be added to your shell startup file so you won't have to run this command each time you log in. ```shell export PATH=/opt/singlestore/singlestore-client:$PATH ``` 4) You may now run the `singlestore` command from anywhere on the filesystem. ```shell singlestore ``` ## Connect using the SingleStore Client 1. For a **package-based installation** of the SingleStore client. ```shell singlestore -h --plugin-dir=/usr/lib/singlestore-client/plugin/ -u ``` 2. For a **tarball-based installation** of the SingleStore client. ```shell singlestore -h --plugin-dir=/path/to/singlestore-client/plugin/ -u ``` *** Modified at: May 11, 2026 Source: [/db/v9.1/security/authentication/authenticate-with-pam-using-active-directory/add-a-new-client-host/](https://docs.singlestore.com/db/v9.1/security/authentication/authenticate-with-pam-using-active-directory/add-a-new-client-host/) (An index of the documentation is available at /llms.txt)