Services Configuration 9 - 41
17. Enter the Proxy Retry Delay as a value in seconds (from 5 - 10 seconds). This is the interval the RADIUS server waits
before making an additional connection attempt. The default delay interval is 5 seconds.
18. Enter the Proxy Retry Count field as a value from 3 - 6. This is the number of retries sent to the proxy server before giving
up the request. The default retry count is 3 attempts.
19. Select the + Add Row button to add a RADIUS server proxy realm name and network address. To delete a proxy server
entry, select the Delete icon on the right-hand side of the table.
20. Enter a 50 character maximum Realm Name. When the access point’s RADIUS server receives a request for a user name,
the server references a table of realms. If the realm is known, the server proxies the request to the RADIUS server.
21. Enter the Proxy server‘s IP Address. This is the address of server checking the information in the user access request. The
proxy server either accepts or rejects the request on behalf of the RADIUS server.
22. Enter the TCP/IP Port Number for the server that acts as a data source for the proxy server. Use the spinner to select a
value from 1024 - 65535. The default port is 1812.
23. Enter the RADIUS client’s Shared Secret for authenticating the RADIUS proxy.
24. Select the Show check box to expose the shared secret’s actual character string. Leave the option unselected to display
the shared secret as a string of asterisks (*).
25. Select the OK button to save the changes. Select the Reset button to revert to the last saved configuration.
26. Select the LDAP and ensure the Activate RADIUS Server Policy button remains selected.
Administrators have the option of using the access point’s RADIUS server to authenticate users against an external LDAP
server resource. An external LDAP user database allows the centralization of user information and reduces administrative
user management overhead. Thus, making the RADIUS authorization process more secure and efficient.
RADIUS is not just a database. It’s a protocol for asking intelligent questions to a user database (like LDAP). LDAP however
is just a database of user credentials used optionally with the RADIUS server to free up resources and manage user
credentials from a secure remote location. It’s the access point’s RADIUS resources that provide the tools to perform user
authentication and authorize users based on complex checks and logic. There’s no way to perform such complex
authorization checks from a LDAP user database alone.
To Next Page
Loading...
