{"id":56313,"date":"2020-02-10T00:00:00","date_gmt":"2020-02-09T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/8-fortinet-getting-started-v6-0-rabota-s-polzovatelyami"},"modified":"2020-02-18T14:04:33","modified_gmt":"2020-02-18T11:04:33","slug":"8-fortinet-getting-started-v6-0-rabota-s-polzovatelyami","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/8-fortinet-getting-started-v6-0-rabota-s-polzovatelyami","title":{"rendered":"8. Fortinet Getting Started v6.0. Working with users","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"8.
\n
\nHello! Welcome to the eighth lesson of the course. Fortinet Getting Started<\/a><\/noindex>. On sixth<\/a><\/noindex> and seventh<\/a><\/noindex> In the previous lessons, we got acquainted with the main security profiles. Now we can release users onto the Internet, protecting them from viruses and regulating access to web resources and applications. Now the question arises about managing user accounts. How can we ensure Internet access for only a specific group of users? How can we prohibit one group of users from visiting certain websites while allowing another? How can we integrate existing user account control solutions with the FortiGate firewall? Today we will discuss these questions and try to practice them.
\n<\/a><\/noindex>
\nFirst, let's look at the authentication methods supported by FortiGate. There are essentially two \u2014 local and remote. <\/p>\n

\"8.
\n
\nThe local method is the simplest form of authentication. In this case, user data is stored locally on the FortiGate. Local users can be grouped together, and access to various resources can be regulated based on users or groups.
\nWhen remote authentication is used, users are authenticated by remote servers. This method is useful when multiple FortiGates need to authenticate the same users, or when an authentication server already exists in the network.<\/p>\n

When a remote server authenticates users, FortiGate sends the user's credentials entered to that server. The server then checks whether such credentials exist in its database. If they do, the user is successfully authenticated in the system. <\/p>\n

It is important to note that in this case, user credentials are not stored on the FortiGate, and the authentication process occurs on the remote server.<\/p>\n

It is also worth mentioning the Fortinet Single Sign-On mechanism. It allows for transparent domain user authentication on FortiGate using data from domain controllers. Unfortunately, discussion of this mechanism is beyond the scope of our course. <\/p>\n

FortiGate supports various types of authentication servers, such as POP3, RADIUS, LDAP, TACACS+. We will explore working with an LDAP server. <\/p>\n

The video covers the basic theory as well as working with local users and the LDAP server. <\/p>\n

\r\n \"Play\r\n
<\/div>\r\n <\/div><\/center>
\nIn the next lesson, we will look at working with logs, specifically exploring the capabilities of FortiAnalyzer. To not miss it, keep an eye on updates on the following channels:<\/p>\n