Cisco 4402 Configuration Guide - Page 41

Step 5: Connection Request Policies - specification

Get Cisco 4402 - Wireless LAN Controller PDF manuals and user guides
UPC - 882658039997
View all Cisco 4402 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 41 highlights

Step 5: Connection Request Policies Connection Request Policies determine where authorisation shall take place according to certain criteria. One policy may authenticate employees locally and forward all students to the RADIUS server associated with the school domain, while another policy directs all other users to the eduroam core. Since the policies are handled in a specific order, it is important that this is done correctly. 1. Users who are to be authenticated locally 2. Users who are to be forwarded to another RADIUS server (several of which can be configured) 3. All other users to be directed to eduroam 1. Right-click on "Connection Request Policy" and select "New Connection Request Policy". 2. Click on "Next" 3. Select "A custom policy", fill in the Policy name (for example, "Local", "School" or "eduroam") and click on "Next". 4. Click on "Add" to add criteria for the connection. Eduroam determines where a user belongs by using the realm which is indicated when the user types username@organisation. In spite of the apparent similarity, there is no connection between realm and e-mail address. However, in most cases it is possible to use a realm corresponding to an e-mail address. The realms used are often agreed in advance. If you have any queries, contact [email protected]. An example of a realm:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
Step 5: Connection Request Policies
Connection Request Policies determine where authorisation shall take place according to certain criteria. One
policy may authenticate employees locally and forward all students to the RADIUS server associated with the
school domain, while another policy directs all other users to the eduroam core. Since the policies are handled
in a specific order, it is important that this is done correctly.
1.
Users who are to be authenticated locally
2.
Users who are to be forwarded to another RADIUS server (several of which can be configured)
3.
All other users to be directed to eduroam
1.
Right-click on “Connection Request Policy” and select “New Connection Request Policy”.
2.
Click on “Next”
3.
Select “A custom policy”, fill in the Policy name (for example, “Local”, “School” or “eduroam”) and click
on “Next”.
4.
Click on “Add” to add criteria for the connection.
Eduroam determines where a user belongs by using the realm which is indicated when the user types
username@organisation
. In spite of the apparent similarity, there is no connection between realm and e-mail
address. However, in most cases it is possible to use a realm corresponding to an e-mail address. The realms
used are often agreed in advance. If you have any queries, contact
.
An example of a realm: