Skip to main content
Mitratech Success Center
Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

Overriding Authentication for Individual Users

  1. Last updated
  2. Save as PDF
Once a default authentication plug-in is configured in TeamConnect, you only need to override the authentication method for users who require a different method. No changes are needed for users using the default authentication.

For details on settings on the user account screen, see Creating or Editing Users.

The example below presumes that your default authentication method is not LDAP, but some individual users do need to authenticate through LDAP. The steps described are similar no matter which method you are using to override.

Account Information.png

To configure an individual user account to use LDAP authentication

  1. Click the Admin tab.
  2. Click the Users link under the tab bar.
  3. Open the desired user account.
  4. From the Authentication drop-down list on the General page, select LDAP TeamConnect Authenticator. The screen refreshes and all fields regarding TeamConnect passwords are removed since a user who is authenticated through LDAP does not need a TeamConnect password.
  5. Click Save.
    LDAP authentication configuration is completed.

The next time the user logs in to TeamConnect, even though the TeamConnect login screen is presented, he or she is actually authenticated through LDAP.

Login behavior when overriding authentication

When you override a user’s authentication method, the login pages the user can use and the credentials the user must enter depend on:

  • The default authentication method for the system.
  • The Authentication setting on the user account.  

Consider the following scenarios:

  1. Default authentication is Standard; user is overridden to LDAP TeamConnect Authenticator
  •   When the user signs in through the standard TeamConnect login page, TeamConnect authenticates the user through LDAP.  
  •   The user must enter LDAP credentials, even though the standard TeamConnect login screen is displayed.  
  •   TeamConnect password fields are removed from the user account because a user who is authenticated through LDAP does not require a TeamConnect application password.
  1. Default authentication is LDAP; user is overridden to Standard Authentication
  •   When the user accesses the main TeamConnect URL, the LDAP login page does not authenticate that user because the user is configured to use Standard Authentication.  
  •   The user must navigate to the standard login URL ( /standardLogin ) and sign in with a TeamConnect application password.  
  •   LDAP credentials are not accepted on the standard login page.

In environments where both LDAP and Standard authentication are in use:

Make sure that users know:

  • Which login URL they should use.
  • Which credentials (LDAP or TeamConnect application password) they must use for their account.
  • In addition, for users who authenticate through LDAP:
    • The username in LDAP must match the username in TeamConnect.
    • The user must be active in TeamConnect.

    If these conditions are not met, the user cannot sign in, even if the LDAP credentials are correct

This is especially important for users whose LDAP and TeamConnect passwords are different.

Note: For more information about the LDAP login flow and default authentication behavior, see LDAP Authentication Plug-in.
  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    This page has no tags.