{"id":7215,"date":"2021-05-18T17:27:15","date_gmt":"2021-05-18T20:27:15","guid":{"rendered":"http:\/\/ec2-54-232-63-254.sa-east-1.compute.amazonaws.com\/?p=7215"},"modified":"2021-09-25T10:09:14","modified_gmt":"2021-09-25T13:09:14","slug":"what-is-integrated-authentication-and-how-does-it-work","status":"publish","type":"post","link":"https:\/\/www.neomind.com.br\/en\/blog\/what-is-integrated-authentication-and-how-does-it-work\/","title":{"rendered":"What is Integrated Authentication and how does it work?"},"content":{"rendered":"\n

A very common scenario nowadays is to have a lot of passwords to access banks, social networks, online stores, Netflix, among thousands of other services. The same applies in the business context, since in our companies we also have to control access credentials for various systems such as email, ERP systems,<\/a> ECM<\/a>, Human Resources, etc. The problem is both for users and for IT administrators who have to manage all these password repositories.<\/p>\n\n\n\n

Currently, for the personal context we have several alternatives for password control, such as the Google Chrome password manager, which, when synchronized with our Google user, allows us to store several passwords. In companies, the dream of users and system administrators is to have a single password authenticated in one place (the so-called Single Sign-on) that allows instant access to all the systems in the organization.<\/p>\n\n\n\n

To assist in this process there are several integrated authentication mechanisms<\/strong>, which, as the name implies, integrate with the company various systems and guarantee the user’s identity without us having to enter it several times.<\/p>\n\n\n\n

How do integrated authentication mechanisms work?<\/strong><\/h2>\n\n\n\n

Basically these systems work as follows:<\/p>\n\n\n\n

  1. The integrated authentication system is configured against a repository of users and passwords, which can be, for example, a password repository of your own or integrated with an Active Directory (repository of users and computers of a Windows domain).<\/li>
  2. When a user accesses an application (in our example, the company ERP), the application checks whether the user is already logged in. If not, it asks the integrated authentication system “Which user is logged in?<\/li>
  3. The integrated authentication system checks whether there is an authenticated user. If not, it requests the user’s credentials (user and password).<\/li>
  4. Once the user is logged into the integrated authentication system, it tells the application which user is logged in.<\/li>
  5. The ERP application in our example receives the user and proceeds to give access to the tool.<\/li>
  6. In case the user accesses another company application, such as the HR system, this new application repeats step 2. However, since the user is already logged into the system, it goes straight to step 4.<\/li><\/ol>\n\n\n\n

    We can see that the operation is relatively simple: the user accesses the system, the system accesses the integrated authentication, and the integrated authentication passes the logged-on user to the system (and if necessary, collects the user’s credentials).<\/p>\n\n\n\n

    Advantages of integrated authentication<\/strong><\/h2>\n\n\n\n

    Integrated authentication mechanisms also allow for a number of advantages, such as:<\/p>\n\n\n\n