1. Docs
  2. Administration
  3. Company settings
  4. Active Directory

Active Directory (LDAP)

With Active Directory sign-in, people use their Windows user name and password to sign in to SmartestQA. Their account is created on first sign-in, and their role and projects follow their AD groups.

5 min read Updated Admins

In short

On this page you can

  • Connect SmartestQA to your domain controllers over ldaps:// with a service account.
  • Map AD groups to the Admin or User role and to projects.
  • Choose what happens to people who are in no mapped group.
  • Test a user name before anyone signs in, without creating an account.
  • Trust your company’s own certificate authority.

How to use it

  1. Open Configuration › Company Settings › Active Directory.
  2. Fill Server addresses, Base DN, Service account DN and password; click Test connection.
  3. Under Groups and roles click Add group for each AD group, with its role and projects.
  4. In Test a user check a real user name: the result shows the role they would get.
  5. Turn on Allow sign-in with Active Directory and click Save.

“Users sign in with their Active Directory password. Accounts are created on first sign-in; role and project access come from AD groups on every sign-in. The local platform administrator always signs in with its local password.” The chip next to the title shows Active or Off; Save saves every block of the page.

Before you start#

  • A service account in AD that can read users and groups.
  • Your domain controllers reachable from SmartestQA on ldaps:// (port 636). For SmartestQA in the cloud, ask your network team to allow the connection.
  • The AD groups whose members should get access, and which projects each group needs.
  • Domains: which company a sign-in belongs to is decided by your email/UPN domains and NetBIOS name. Only SmartestQA can set these: write to info@smartestqa.ai with your domains.

Connection#

FieldWhat to enterWho can change it
Allow sign-in with Active DirectoryThe main switch.Admins
Server addresses“ldaps:// addresses, separated by space or comma; tried in order.” For example ldaps://dc1.company.local:636 ldaps://dc2.company.local:636.Admins
Base DNWhere users are searched, for example DC=company,DC=local.Admins
Service account DNFor example CN=svc-smartest,OU=Service Accounts,DC=company,DC=local.Admins
Service account passwordIts password. Once saved: “Saved. Leave empty to keep it.” If you change the server addresses or the service account, enter the password again.Admins
E-mail / UPN domains“Used to find this company when a new user signs in with user@domain.” For example company.com, company.local.SmartestQA only
NetBIOS domain“For sign-in as DOMAIN\user.” For example COMPANY.SmartestQA only
Sign-ins without a domain (only "user") go to this companyFor a single-company installation.SmartestQA only

Click Test connection: it uses the values on screen. “Connection successful.” with the time in ms, or the reason (see Connection errors). Users signed in with AD shows how many accounts are linked to AD.

Groups and roles#

“Enter a group as its full DN or just its name (CN). If several groups match, the most privileged role wins; projects are combined. Access granted here is removed when the user leaves the group; access given by hand is kept.”

FieldWhat it doesDefault
AD group · Role · ProjectsOne row per group (Add group). Role: Admin or User. Projects: the projects members get.New row: User, no projects
Role when no group matchesThe role of people in none of the groups, or Do not allow sign-in.Do not allow sign-in
Include nested groupsMembers of groups inside a mapped group count as members.On
Create the account on first sign-inOff: only people who already have a SmartestQA account can sign in with AD.On

“No groups mapped yet. Without a mapping or default role nobody can sign in.” The Super Admin role can never be granted from AD.

Role and projects at sign-inDecided again at every AD sign-in
matching groups = mapped groups the user is in (nested groups too, if switched on)
role            = the most privileged role among matching groups      (Admin above User)
                  none match → Role when no group matches
                  that is "Do not allow sign-in" → sign-in refused
projects        = all projects of the matching groups
                  + projects an admin assigned by hand (kept)
                  − projects from groups the user has left

Example: mappings Smartest-QA → User, projects Web Shop and Mobile App; Smartest-Leads → Admin, project Web Shop. Ayşe is in both: she gets Admin and both projects. Can is only in Smartest-QA and was given project Backoffice by hand: he gets User with Web Shop, Mobile App and Backoffice. If Can leaves Smartest-QA and the default is “Do not allow sign-in”, his next sign-in is refused.

Test a user#

“Uses the settings on this screen without saving. No account is created and no session is opened.”

  1. Enter a user name

    User name: jdoe, DOMAIN\jdoe or jdoe@company.local. Password (optional): with a password the test also checks it.

  2. Click Test

    The result lists the user’s DN, E-mail, the Role they would get (“default role” if no group matched) and their Groups. A failure shows the reason.

Advanced#

FieldWhat it changesDefault
User search filter“{0} = user name, {1} = full sign-in (UPN / e-mail). Empty = Active Directory default (disabled accounts excluded).” Must contain {0} or {1}.Empty
E-mail attribute · Display name attribute · First name attribute · Last name attributeWhich AD attributes fill the SmartestQA account.mail · displayName · givenName · sn
Connect timeout (ms) · Read timeout (ms)How long SmartestQA waits for a domain controller.5000 · 10000
Company CA certificate (PEM)“For ldaps:// with an internal certificate authority. Empty = the server trust store.”Empty
Do not verify the server certificate (testing only)Skips the certificate check. SmartestQA only.Off
Allow unencrypted ldap:// (passwords travel in clear text)Allows ldap:// addresses. SmartestQA only.Off

Keep certificate checks on

“Passwords could be intercepted by anyone who can impersonate the directory server. Use a CA certificate in production.” Paste your CA certificate in PEM instead of turning the check off.

How sign-in works#

  • People sign in on the normal SmartestQA sign-in page with their AD user name (or email) and AD password.
  • First sign-in creates the account, if Create the account on first sign-in is on. It counts against your licence’s user limit; when the limit is reached the user sees “The user limit of your licence has been reached. Ask your administrator.”
  • Existing SmartestQA accounts are linked on their first AD sign-in when the AD email or UPN equals the account’s email.
  • Once linked, AD decides: if AD refuses the password, the account is locked or disabled, or AD cannot be reached, the sign-in is refused. There is no fallback to a SmartestQA password.
  • Too many wrong passwords for one sign-in name (5 in 15 minutes) or from one network address (30 in 15 minutes) pause AD sign-ins for it, so SmartestQA never locks the AD account.
  • Deactivating the user in Users blocks them even if AD would accept them: “Your SmartestQA account is deactivated. Ask your administrator.”

If something goes wrong#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai