Raritan TeleReach TR361 User Manual

Also see for IP-Reach IPR-M1: User manual Specifications

Contents

54 IP-R EACH USER M ANUALRemote Authentication ImplementationIntroductionNote to CommandCenter UsersIf you plan to configure IP-Reach to be integrated with and controlled by Raritan’s CommandCentermanagement appliance, this section of the User Manual does not apply to you. When an IP-Reach unit iscontrolled by CommandCenter, CommandCenter determines the allowed users and groups. Please refer toyour CommandCenter User Guide.Note to Raritan Customers Upgrading from Previous Firmware VersionsIf you have previously implemented RADIUS authentication on Raritan products such as Dominion KSXand IP-Reach running legacy firmware versions earlier than v3.2, read this entire section carefully.Beginning with firmware version v3.2 and above, the implementation of external authentication haschanged significantly to provide more flexible and powerful configurations.Supported ProtocolsTo simplify management of usernames and passwords, IP-Reach is able to forward authentication requeststo an external authentication server. IP-Reach supports two external authentication protocols: LDAP andRADIUS.Note on Microsoft Active DirectoryMicrosoft Active Directory uses the LDAP protocol natively, and can function as an LDAP server andauthentication source for IP-Reach. If it has the IAS (Internet Authorization Server) component, aMicrosoft Active Directory server can also serve as a RADIUS authentication source.Remote Authentication ImplementationPriorityWhen a user tries to authenticate to an IP-Reach unit that is configured for external authentication, IP-Reach first checks its own internal user database for that username. If the username is not found in the IP-Reach internal database, the request is forwarded to the external authentication server.• If Username is not found in IP-Reach internal database: Request is forwarded to externalauthentication server to determine whether the login is allowed or denied.• If Username is found in IP-Reach internal database and Password is correct: Login is allowed.• If Username is not found in IP-Reach internal database and Password is incorrect: Login isdenied; the request does NOT get forwarded to the external authentication server.