Initial Considerations

You can customize the installation of the Nintex RPA Platform according to your organization's network and security policies. Throughout this guide, instructions and requirements will vary based on the following primary considerations:

Make sure to review System architecture and requirements to ensure your environment is set and ready for the installation.

It is recommended that the service user has a static password.

If it is part of a password-rotation cycle, a manual update to many of the components will be required every time the password changes.

You can install Nintex RPA Server using either:

  • Username and password authentication: Client applications (including unattended/attended robots, Studio, and Console) can connect to the Nintex RPA server using usernames/passwords configured specifically for the RPA platform and defined in the Admin Tool

  • Domain authentication (also referred to as Kerberos): Client applications can connect to the Nintex RPA server using credentials defined in Windows Active Directory. Also referred to as Single Sign-on.

You can configure the Nintex database to use either:

  • SQL authentication: The Nintex RPA Server can connect to the Nintex database server using username and password configured specifically for the database server, and defined in SQL Server Management Studio.

    The RPA DB collation needs to be CI (Case Insensitive). CS isn't supported.

  • Windows authentication – The Nintex RPA server can connect to the Nintex database using network credentials defined in Windows Active Directory.

Either database authentication method can be used with either RPA platform authentication method.

There are two different automation contexts:

  • Attended: This doesn't require the installation of Console Plus.

  • Unattended: This requires the installation of Console Plus.

Consider RPA System Hardening to reduce IT vulnerability and the possibility of being compromised.

See RPA System Hardening and Vulnerability Management.

The Nintex platform includes the option to secure communications using SSL/TLS .

If you want to install with SSL/TLS , you can provide the organization's CA and certificate or generate them using the RPA Server installation wizard (yes, we can do it for you).

If you already have the organization’s CA and certificate, just make sure they meet the TSL/SSL requirements.

If you are planning to create a CA and certificate before installing the RPA Server and you need the guidance, see SSL/TLS Additional Procedures.

TLS v1.2 is supported.

The Nintex platform supports the option to install two (2) or more RPA servers. This is the recommended configuration in a production environment.