Logins

The Logins page allows an administrator to grant application access to a security principal. A security principal may be authenticated by Windows or SQL Server. A Windows authenticated user is identified using the structure domain/user. These users are created and maintained in the Microsoft Active Directory (AD) which allows users to access resources across the domain. A SQL Server authenticated user is identified simply by their login and may only access resources on the database server. Regardless of authentication method, adding a user to the Logins is the first step in granting access.

In this article

Logins

Field's Description

  • Login Name The login of the security principal. If Windows authentication is true, use the format domain/user. The name will be validated against the AD. If Windows authentication is false, enter the login name. If the login name does not exist, it will be created.

  • Created Date Date in which Entity object was created.

  • Default Database Name The default database sets the context of database operations. Select from the drop-down list to change or use the default.

  • Default Language The default language controls the database messages. Select from the drop-down list to change or use the default (i.e., English).

  • Is Windows Authentication When checked, the login name will be authenticated using Microsoft Active Directory (AD). When checked, the login name will be authenticated using SQL Server. Default is True.

  • Security Access Select either Grant Access or Deny Access. Default is Grant Access.

  • Password If Windows Authentication is unchecked (i.e., false), a password must be supplied to create the Login Name in the SQL Server. Click here for password complexity guidelines. Has no effect if  Windows Authentication is checked.

  • Confirm Password Re-enter the Password for confirmation.