The proxy feature forwards
authentication (and accounting messages) to another server. It can
be used in enabling roaming users to be authenticated from their
own server. Proxying is configured by specifying proxy authentication
for a user or realm and pointing authentication to a remote server
defined as a peer in the forwarding server’s configuration.
As shown in the figure below, when your server is in a foreign
network to a mobile node, your server forwards the request. The
request may be forwarded through one or more remote proxy servers
before it reaches the mobile node’s home server. You may
administer the remote server, or another organization may maintain
it.
To Proxy
Requests
to a Another Server |
 |
Access the Mobile
AAA Server Manager.
Select Peers from the Navigation
Tree located in the left frame of the browser and then select the New Peer link
and the Peer Attributes screen will appear.
Enter the Fully-Qualified-Domain-Name
of the remote server in the FQDN field.
In the Identity Port and Connection Port, enter the port of the remote server. These fields should
hold the same value, unless TLS is used
From the Type drop-down list,
select Diameter Server.
Depending on your configuration
requirements, you may input values in the Security or Connection drop-down
lists or in the IP Address list box. You can accept the default
values for a standard agent configuration. See the Administrators
Guide for more information about these fields.
Select the Create button.
Select the Save button.
Select Realms from the
Navigation frame.
Either select the New realm
link and then create a new realm or select an existing realm’s
link.
When creating the new realm
or modifying an existing realm, select PROXY from the Authentication
Type drop-down list.
In the FQDN or filename text box, enter the Fully-Qualified-Domain-Name
of the remote server.
Select the Create button.
Select the Save button.
Printable version
