-
Enter and confirm the existing Admin Password. This is the
password used to access Reveal, Workbench, KAgent, and GAdmin as the
default administrative user.
The password provided here must match the existing cluster’s admin password.
-
Select an SSL Mode that best aligns with the existing cluster’s
SSL configuration:
- Cert/key setup not required — Kinetica will not require SSL certificate/key creation/upload but there will be no updates to security configuration settings
- User-provided cert/key per node — user must upload an SSL certificate and key for each node; Kinetica copies the cert/key pair to /opt/gpudb/certs, enables HTTPD, and configures HTTPD to use HTTPS
- Generate self-signed cert/key per node — KAgent generates a self-signed certificate and key for each node and places it in /opt/gpudb/certs, enables HTTPD, and configures HTTPD to use HTTPS
-
Select the current Authentication type used for the existing
cluster and fill the fields as necessary:
- None — no authentication or authorization
- LDAP — configures Kinetica to authenticate via LDAP; requires authentication to connect to the database, enables authorization, enables external authentication, automatically creates users in the database for LDAP users, and automatically grants roles in the database to LDAP users
- Active Directory — configures Kinetica to authenticate via Microsoft Active Directory; requires authentication to connect to the database, enables authorization, enables external authentication, automatically creates users in the database for Active Directory users, and automatically grants roles in the database to Active Directory users
- Kerberos — configures Kinetica to authenticate via Kerberos; requires authentication to connect to the database, enables authorization, enables external authentication, automatically creates users in the database for Kerberos users, and automatically grants roles in the database to Kerberos users
- Click Next.