Enhanced Algorithm for Modular Isomorphism Problem Resolution in Small Group Orders

Abstract

Radius centralizes logins and passwords. This is a server protocol. It should be noted that the server, Radius, manages authentication for clients, routers and switches. Radius is simply a remote authentication protocol used to centralize authentication data and manage user connections to remote services. This protocol relies primarily on a server (DARIUS server), linked to an identification base (database, LDAP directory, etc.). A Radius client, called NAS (Network Access Server), acting as intermediary between the end-user and the server. All transactions between the Radius client and the server are encrypted. It works on the basis of a scenario similar to : a user sends a request to the NAS to authorize a remote connection. The NAS in turn forwards the request to the Radius server. The latter consults the requested identification database to find out the type of identification scenario requested for the user. Either the current scenario is suitable, or another identification method is requested from the user. This protocol thus returns one of the four responses we'll discuss in the rest of this article : ACCEPT : identification successful, REJECT : identification failed, CHALLENGE : the Radius server requests additional information from the user and proposes a challenge. Following the above authentication phase, an authentication phase begins, in which the server returns the user's authorizations. In this article, as a network manager, we're concerned with setting up means of access control, and to do this, we have to square a kind of circle : simplicity for the user, reliability of the mechanisms, high level of security, all while using available standards as much as possible.