Overview of User Authentication

From TeamServer ER/Studio
Jump to: navigation, search

Go Up to Overview of Security

When you try to log in to Team Server, Team Server follows these steps after it confirms that your credentials are valid:

  1. If there is a Team Server user connection associated with your account, Team Server logs you in as a social user.
  2. If there is no Team Server user connection associated with your account, but there is a concurrent user connection available, Team Server logs you in as a non-social user.
  3. If you are trying to log in with the base super user connection, Team Server logs you in as a non-social user.
  4. If there is no concurrent user connection available, you cannot access Team Server.

Inactive users are automatically timed out 30 minutes after the last user interaction, to free concurrent user connections even if users forget to close the web browser or log out. See Modifying the User Session Idle Time Limit.

Note: Each web browser manage user sessions in a different way. Depending on your web browser, you might not be able to log in using the same user credentials for two different sessions, or using two different sets of user credentials. Some web browsers treat windows and tabs as one instance, and will not let you run two sessions simultaneously. However, you can open multiple instances of Internet Explorer and log in multiple time using the same concurrent user credentials, or create several different sessions using a mix of concurrent and social connections.

See Also