3 # Whatever you do, do NOT set 'Auth-Type := EAP'. The server
4 # is smart enough to figure this out on its own. The most
5 # common side effect of setting 'Auth-Type := EAP' is that the
6 # users then cannot use ANY other authentication method.
11 # Invoke the default supported EAP type when
12 # EAP-Identity response is received.
14 # The incoming EAP messages DO NOT specify which EAP
15 # type they will be using, so it MUST be set here.
17 # For now, only one default EAP type may be used at a time.
19 # If the EAP-Type attribute is set by another module,
20 # then that EAP type takes precedence over the
21 # default type configured here.
23 default_eap_type = md5
25 # A list is maintained to correlate EAP-Response
26 # packets with EAP-Request packets. After a
27 # configurable length of time, entries in the list
28 # expire, and are deleted.
32 # There are many EAP types, but the server has support
33 # for only a limited subset. If the server receives
34 # a request for an EAP type it does not support, then
35 # it normally rejects the request. By setting this
36 # configuration to "yes", you can tell the server to
37 # instead keep processing the request. Another module
38 # MUST then be configured to proxy the request to
39 # another RADIUS server which supports that EAP type.
41 # If another module is NOT configured to handle the
42 # request, then the request will still end up being
44 ignore_unknown_eap_types = no
46 # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given
47 # a User-Name attribute in an Access-Accept, it copies one
48 # more byte than it should.
50 # We can work around it by configurably adding an extra
52 cisco_accounting_username_bug = no
57 # We do NOT recommend using EAP-MD5 authentication
58 # for wireless connections. It is insecure, and does
59 # not provide for dynamic WEP keys.
66 # We do not recommend using LEAP in new deployments. See:
67 # http://www.securiteam.com/tools/5TP012ACKE.html
69 # Cisco LEAP uses the MS-CHAP algorithm (but not
70 # the MS-CHAP attributes) to perform it's authentication.
72 # As a result, LEAP *requires* access to the plain-text
73 # User-Password, or the NT-Password attributes.
74 # 'System' authentication is impossible with LEAP.
81 # Currently, this is only permitted inside of EAP-TTLS,
82 # or EAP-PEAP. The module "challenges" the user with
83 # text, and the response from the user is taken to be
86 # Proxying the tunneled EAP-GTC session is a bad idea,
87 # the users password will go over the wire in plain-text,
91 # The default challenge, which many clients
93 #challenge = "Password: "
95 # The plain-text response which comes back
96 # is put into a User-Password attribute,
97 # and passed to another module for
98 # authentication. This allows the EAP-GTC
99 # response to be checked against plain-text,
100 # or crypt'd passwords.
102 # If you say "Local" instead of "PAP", then
103 # the module will look for a User-Password
104 # configured for the request, and do the
105 # authentication itself.
112 # To generate ctest certificates, run the script
114 # ../scripts/certs.sh
116 # The documents on http://www.freeradius.org/doc
117 # are old, but may be helpful.
121 # http://www.dslreports.com/forum/remark,9286052~mode=flat
124 # private_key_password = whatever
125 # private_key_file = ${raddbdir}/certs/cert-srv.pem
127 # If Private key & Certificate are located in
128 # the same file, then private_key_file &
129 # certificate_file must contain the same file
131 # certificate_file = ${raddbdir}/certs/cert-srv.pem
133 # Trusted Root CA list
134 # CA_file = ${raddbdir}/certs/demoCA/cacert.pem
136 # dh_file = ${raddbdir}/certs/dh
137 # random_file = ${raddbdir}/certs/random
140 # This can never exceed the size of a RADIUS
141 # packet (4096 bytes), and is preferably half
142 # that, to accomodate other attributes in
143 # RADIUS packet. On most APs the MAX packet
144 # length is configured between 1500 - 1600
145 # In these cases, fragment size should be
148 # fragment_size = 1024
150 # include_length is a flag which is
151 # by default set to yes If set to
152 # yes, Total Length of the message is
153 # included in EVERY packet we send.
154 # If set to no, Total Length of the
155 # message is included ONLY in the
156 # First packet of a fragment series.
158 # include_length = yes
160 # Check the Certificate Revocation List
162 # 1) Copy CA certificates and CRLs to same directory.
163 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
164 # 'c_rehash' is OpenSSL's command.
165 # 3) Add 'CA_path=<CA certs&CRLs directory>'
166 # to radiusd.conf's tls section.
167 # 4) uncomment the line below.
172 # If check_cert_cn is set, the value will
173 # be xlat'ed and checked against the CN
174 # in the client certificate. If the values
175 # do not match, the certificate verification
176 # will fail rejecting the user.
178 # check_cert_cn = %{User-Name}
181 # The TTLS module implements the EAP-TTLS protocol,
182 # which can be described as EAP inside of Diameter,
183 # inside of TLS, inside of EAP, inside of RADIUS...
185 # Surprisingly, it works quite well.
187 # The TTLS module needs the TLS module to be installed
188 # and configured, in order to use the TLS tunnel
189 # inside of the EAP packet. You will still need to
190 # configure the TLS module, even if you do not want
191 # to deploy EAP-TLS in your network. Users will not
192 # be able to request EAP-TLS, as it requires them to
193 # have a client certificate. EAP-TTLS does not
194 # require a client certificate.
197 # The tunneled EAP session needs a default
198 # EAP type which is separate from the one for
199 # the non-tunneled EAP module. Inside of the
200 # TTLS tunnel, we recommend using EAP-MD5.
201 # If the request does not contain an EAP
202 # conversation, then this configuration entry
204 # default_eap_type = md5
206 # The tunneled authentication request does
207 # not usually contain useful attributes
208 # like 'Calling-Station-Id', etc. These
209 # attributes are outside of the tunnel,
210 # and normally unavailable to the tunneled
211 # authentication request.
213 # By setting this configuration entry to
214 # 'yes', any attribute which NOT in the
215 # tunneled authentication request, but
216 # which IS available outside of the tunnel,
217 # is copied to the tunneled request.
219 # allowed values: {no, yes}
220 # copy_request_to_tunnel = no
222 # The reply attributes sent to the NAS are
223 # usually based on the name of the user
224 # 'outside' of the tunnel (usually
225 # 'anonymous'). If you want to send the
226 # reply attributes based on the user name
227 # inside of the tunnel, then set this
228 # configuration entry to 'yes', and the reply
229 # to the NAS will be taken from the reply to
230 # the tunneled request.
232 # allowed values: {no, yes}
233 # use_tunneled_reply = no
237 # The tunneled EAP session needs a default EAP type
238 # which is separate from the one for the non-tunneled
239 # EAP module. Inside of the TLS/PEAP tunnel, we
240 # recommend using EAP-MS-CHAPv2.
242 # The PEAP module needs the TLS module to be installed
243 # and configured, in order to use the TLS tunnel
244 # inside of the EAP packet. You will still need to
245 # configure the TLS module, even if you do not want
246 # to deploy EAP-TLS in your network. Users will not
247 # be able to request EAP-TLS, as it requires them to
248 # have a client certificate. EAP-PEAP does not
249 # require a client certificate.
252 # The tunneled EAP session needs a default
253 # EAP type which is separate from the one for
254 # the non-tunneled EAP module. Inside of the
255 # PEAP tunnel, we recommend using MS-CHAPv2,
256 # as that is the default type supported by
258 # default_eap_type = mschapv2
260 # the PEAP module also has these configuration
261 # items, which are the same as for TTLS.
262 # copy_request_to_tunnel = no
263 # use_tunneled_reply = no
265 # When the tunneled session is proxied, the
266 # home server may not understand EAP-MSCHAP-V2.
267 # Set this entry to "no" to proxy the tunneled
268 # EAP-MSCHAP-V2 as normal MSCHAPv2.
269 # proxy_tunneled_request_as_eap = yes
273 # This takes no configuration.
275 # Note that it is the EAP MS-CHAPv2 sub-module, not
276 # the main 'mschap' module.
278 # Note also that in order for this sub-module to work,
279 # the main 'mschap' module MUST ALSO be configured.
281 # This module is the *Microsoft* implementation of MS-CHAPv2
282 # in EAP. There is another (incompatible) implementation
283 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not