Domain's Login Section

In this section you define the login providers for those accessing the data from applications, the Data Login Provider, and a provider that is used specifically for developers.

The Data Login Provider handles the authentication of users accessing the server from their applications. Typically the user login details are defined in a database table using a DbTableLoginProvider, but on a smaller system you might just use a StaticLoginProvider.

The Developer Login Provider is an optional login provider designed to let developers have partial access without giving them full admin privileges.

The following is a quick breakdown of the available Login Providers selectable in the Data Login Provider and Developer Login Provider selection boxes.

StaticLoginProvider is the simplest of the login providers, and the most useful for admin/developer login, or in the early development phase of your project. It works by simply letting you specify a list of valid usernames and passwords that will be accepted. This is the default login provider for all logins on a freshly installed Relativity Server or a freshly created domain.

DbTableLoginProvider validates the username and password against a table in your database. It allows you to select a table from your schema, as well as two fields from that table that contain usernames and passwords, respectively. The Login will be verified by selecting from the table, and access will be granted if a row with matching username and password is found.

DbCommandLoginProvider lets you validate the login against your database, but instead of simply querying a table, it will execute a command defined in your schema. You could implement the command to run a query, execute a stored procedure, or perform more some complex SQL. In order to qualify, the command must take two parameters (username and password) and return a Boolean.

LdapLoginProvider is the most complex one of the available login provider options. It can be used to connect Relativity to an existing LDAP server in your organization to validate logins. This can be very useful if you want your application to automatically share usernames and passwords with other non-Relativity, non-Data Abstract services in your company. Getting into the details of LDAP would go beyond the scope of this text, but if your organization is using LDAP, your LDAP administrator should be familiar with the required options.

AdminServicesLogin option, available for the per-domain login providers, simply indicates that rather than using separate logins, the same settings as for the server-wide Admin Login should be used here.