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.
8 # $Id: eap.conf,v 1.4.4.5 2007/04/20 11:58:45 aland Exp $
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
138 # For DH cipher suites to work, you have to
139 # run OpenSSL to create the DH file first:
141 # openssl dhparam -out certs/dh 1024
143 # dh_file = ${raddbdir}/certs/dh
144 # random_file = ${raddbdir}/certs/random
147 # This can never exceed the size of a RADIUS
148 # packet (4096 bytes), and is preferably half
149 # that, to accomodate other attributes in
150 # RADIUS packet. On most APs the MAX packet
151 # length is configured between 1500 - 1600
152 # In these cases, fragment size should be
155 # fragment_size = 1024
157 # include_length is a flag which is
158 # by default set to yes If set to
159 # yes, Total Length of the message is
160 # included in EVERY packet we send.
161 # If set to no, Total Length of the
162 # message is included ONLY in the
163 # First packet of a fragment series.
165 # include_length = yes
167 # Check the Certificate Revocation List
169 # 1) Copy CA certificates and CRLs to same directory.
170 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
171 # 'c_rehash' is OpenSSL's command.
172 # 3) Add 'CA_path=<CA certs&CRLs directory>'
173 # to radiusd.conf's tls section.
174 # 4) uncomment the line below.
179 # If check_cert_issuer is set, the value will
180 # be checked against the DN of the issuer in
181 # the client certificate. If the values do not
182 # match, the cerficate verification will fail,
183 # rejecting the user.
185 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
188 # If check_cert_cn is set, the value will
189 # be xlat'ed and checked against the CN
190 # in the client certificate. If the values
191 # do not match, the certificate verification
192 # will fail rejecting the user.
194 # This check is done only if the previous
195 # "check_cert_issuer" is not set, or if
196 # the check succeeds.
198 # check_cert_cn = %{User-Name}
200 # Set this option to specify the allowed
201 # TLS cipher suites. The format is listed
202 # in "man 1 ciphers".
203 # cipher_list = "DEFAULT"
206 # The TTLS module implements the EAP-TTLS protocol,
207 # which can be described as EAP inside of Diameter,
208 # inside of TLS, inside of EAP, inside of RADIUS...
210 # Surprisingly, it works quite well.
212 # The TTLS module needs the TLS module to be installed
213 # and configured, in order to use the TLS tunnel
214 # inside of the EAP packet. You will still need to
215 # configure the TLS module, even if you do not want
216 # to deploy EAP-TLS in your network. Users will not
217 # be able to request EAP-TLS, as it requires them to
218 # have a client certificate. EAP-TTLS does not
219 # require a client certificate.
222 # The tunneled EAP session needs a default
223 # EAP type which is separate from the one for
224 # the non-tunneled EAP module. Inside of the
225 # TTLS tunnel, we recommend using EAP-MD5.
226 # If the request does not contain an EAP
227 # conversation, then this configuration entry
229 # default_eap_type = md5
231 # The tunneled authentication request does
232 # not usually contain useful attributes
233 # like 'Calling-Station-Id', etc. These
234 # attributes are outside of the tunnel,
235 # and normally unavailable to the tunneled
236 # authentication request.
238 # By setting this configuration entry to
239 # 'yes', any attribute which NOT in the
240 # tunneled authentication request, but
241 # which IS available outside of the tunnel,
242 # is copied to the tunneled request.
244 # allowed values: {no, yes}
245 # copy_request_to_tunnel = no
247 # The reply attributes sent to the NAS are
248 # usually based on the name of the user
249 # 'outside' of the tunnel (usually
250 # 'anonymous'). If you want to send the
251 # reply attributes based on the user name
252 # inside of the tunnel, then set this
253 # configuration entry to 'yes', and the reply
254 # to the NAS will be taken from the reply to
255 # the tunneled request.
257 # allowed values: {no, yes}
258 # use_tunneled_reply = no
261 ##################################################
263 # !!!!! WARNINGS for Windows compatibility !!!!!
265 ##################################################
267 # If you see the server send an Access-Challenge,
268 # and the client never sends another Access-Request,
273 # The server certificate has to have special OID's
274 # in it, or else the Microsoft clients will silently
275 # fail. See the "scripts/xpextensions" file for
276 # details, and the following page:
278 # http://support.microsoft.com/kb/814394/en-us
280 # For additional Windows XP SP2 issues, see:
282 # http://support.microsoft.com/kb/885453/en-us
284 # Note that we do not necessarily agree with their
285 # explanation... but the fix does appear to work.
287 ##################################################
290 # The tunneled EAP session needs a default EAP type
291 # which is separate from the one for the non-tunneled
292 # EAP module. Inside of the TLS/PEAP tunnel, we
293 # recommend using EAP-MS-CHAPv2.
295 # The PEAP module needs the TLS module to be installed
296 # and configured, in order to use the TLS tunnel
297 # inside of the EAP packet. You will still need to
298 # configure the TLS module, even if you do not want
299 # to deploy EAP-TLS in your network. Users will not
300 # be able to request EAP-TLS, as it requires them to
301 # have a client certificate. EAP-PEAP does not
302 # require a client certificate.
305 # The tunneled EAP session needs a default
306 # EAP type which is separate from the one for
307 # the non-tunneled EAP module. Inside of the
308 # PEAP tunnel, we recommend using MS-CHAPv2,
309 # as that is the default type supported by
311 # default_eap_type = mschapv2
313 # the PEAP module also has these configuration
314 # items, which are the same as for TTLS.
315 # copy_request_to_tunnel = no
316 # use_tunneled_reply = no
318 # When the tunneled session is proxied, the
319 # home server may not understand EAP-MSCHAP-V2.
320 # Set this entry to "no" to proxy the tunneled
321 # EAP-MSCHAP-V2 as normal MSCHAPv2.
322 # proxy_tunneled_request_as_eap = yes
326 # This takes no configuration.
328 # Note that it is the EAP MS-CHAPv2 sub-module, not
329 # the main 'mschap' module.
331 # Note also that in order for this sub-module to work,
332 # the main 'mschap' module MUST ALSO be configured.
334 # This module is the *Microsoft* implementation of MS-CHAPv2
335 # in EAP. There is another (incompatible) implementation
336 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not