Sign inTry Free

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

Add a New Client Host

On this page

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 

    sudo yum install krb5-user

    Debian 

    sudo apt install krb5-user

  2. Enter the domain that will be connected to the default Kerberos realm.

  3. Enter the Kerberos authentication server.

  4. Enter the administrative server.

  5. The [realms] section in the /etc/krb5.conf file on this host will now resemble the following.

    [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.

    kinit user1@S2.LOCAL
    Password for user1@S2.LOCAL:
    klist
    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

Connect using the SingleStore Client

  1. For a package-based installation of the SingleStore client.

    singlestore -h<hostname> --plugin-dir=/usr/lib/singlestore-client/plugin/ -u<username>

  2. For a tarball-based installation of the SingleStore client.

    singlestore -h<hostname> --plugin-dir=/path/to/singlestore-client/plugin/ -u<username>

Last modified: January 9, 2023

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK