| 1 |
# -*- text -*- |
| 2 |
## |
| 3 |
## eap.conf -- Configuration for EAP types (PEAP, TTLS, etc.) |
| 4 |
## |
| 5 |
## $Id: 499614bb8e296ec0078498ec4120867430f794cd $ |
| 6 |
|
| 7 |
####################################################################### |
| 8 |
# |
| 9 |
# Whatever you do, do NOT set 'Auth-Type := EAP'. The server |
| 10 |
# is smart enough to figure this out on its own. The most |
| 11 |
# common side effect of setting 'Auth-Type := EAP' is that the |
| 12 |
# users then cannot use ANY other authentication method. |
| 13 |
# |
| 14 |
eap { |
| 15 |
# Invoke the default supported EAP type when |
| 16 |
# EAP-Identity response is received. |
| 17 |
# |
| 18 |
# The incoming EAP messages DO NOT specify which EAP |
| 19 |
# type they will be using, so it MUST be set here. |
| 20 |
# |
| 21 |
# For now, only one default EAP type may be used at a time. |
| 22 |
# |
| 23 |
# If the EAP-Type attribute is set by another module, |
| 24 |
# then that EAP type takes precedence over the |
| 25 |
# default type configured here. |
| 26 |
# |
| 27 |
default_eap_type = md5 |
| 28 |
|
| 29 |
# A list is maintained to correlate EAP-Response |
| 30 |
# packets with EAP-Request packets. After a |
| 31 |
# configurable length of time, entries in the list |
| 32 |
# expire, and are deleted. |
| 33 |
# |
| 34 |
timer_expire = 60 |
| 35 |
|
| 36 |
# |
| 37 |
# Some supplicants may misbehave by starting many thousands |
| 38 |
# of EAP sessions, but never finishing them. These sessions |
| 39 |
# can cause the server to hit 'max_sessions' very quickly. |
| 40 |
# The 'timer_expire' configuration above does not help as |
| 41 |
# much as it could, because the old (duplicate) session |
| 42 |
# should be deleted as soon as the new one comes in. |
| 43 |
# |
| 44 |
# If you set the 'dedup_key' below, whenever the EAP module |
| 45 |
# starts a new session, it will check for a previous session |
| 46 |
# which has the same dedup key. If a previous session |
| 47 |
# is found, it is deleted. |
| 48 |
# |
| 49 |
# Setting this configuration item may cause issues if the |
| 50 |
# same device uses multiple EAP sessions at the same time. |
| 51 |
# But that device behavior should be rare to non-existent. |
| 52 |
# |
| 53 |
# The configuration item is commented out so that upgrades |
| 54 |
# do not change existing behavior. |
| 55 |
# |
| 56 |
# dedup_key = "%{Calling-Station-Id}" |
| 57 |
|
| 58 |
# There are many EAP types, but the server has support |
| 59 |
# for only a limited subset. If the server receives |
| 60 |
# a request for an EAP type it does not support, then |
| 61 |
# it normally rejects the request. By setting this |
| 62 |
# configuration to "yes", you can tell the server to |
| 63 |
# instead keep processing the request. Another module |
| 64 |
# MUST then be configured to proxy the request to |
| 65 |
# another RADIUS server which supports that EAP type. |
| 66 |
# |
| 67 |
# If another module is NOT configured to handle the |
| 68 |
# request, then the request will still end up being |
| 69 |
# rejected. |
| 70 |
# |
| 71 |
ignore_unknown_eap_types = no |
| 72 |
|
| 73 |
# Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given |
| 74 |
# a User-Name attribute in an Access-Accept, it copies one |
| 75 |
# more byte than it should. |
| 76 |
# |
| 77 |
# We can work around it by configurably adding an extra |
| 78 |
# zero byte. |
| 79 |
# |
| 80 |
cisco_accounting_username_bug = no |
| 81 |
|
| 82 |
# Help prevent DoS attacks by limiting the number of |
| 83 |
# sessions that the server is tracking. For simplicity, |
| 84 |
# this is taken from the "max_requests" directive in |
| 85 |
# radiusd.conf. |
| 86 |
# |
| 87 |
max_sessions = ${max_requests} |
| 88 |
|
| 89 |
|
| 90 |
############################################################ |
| 91 |
# |
| 92 |
# Supported EAP-types |
| 93 |
# |
| 94 |
|
| 95 |
|
| 96 |
# EAP-MD5 |
| 97 |
# |
| 98 |
# We do NOT recommend using EAP-MD5 authentication |
| 99 |
# for wireless connections. It is insecure, and does |
| 100 |
# not provide for dynamic WEP keys. |
| 101 |
# |
| 102 |
md5 { |
| 103 |
} |
| 104 |
|
| 105 |
|
| 106 |
# EAP-pwd -- secure password-based authentication |
| 107 |
# |
| 108 |
#pwd { |
| 109 |
# group = 19 |
| 110 |
|
| 111 |
# server_id = [email protected] |
| 112 |
|
| 113 |
# This has the same meaning as for TLS. |
| 114 |
# |
| 115 |
# fragment_size = 1020 |
| 116 |
|
| 117 |
# The virtual server which determines the |
| 118 |
# "known good" password for the user. |
| 119 |
# Note that unlike TLS, only the "authorize" |
| 120 |
# section is processed. EAP-PWD requests can be |
| 121 |
# distinguished by having a User-Name, but |
| 122 |
# no User-Password, CHAP-Password, EAP-Message, etc. |
| 123 |
# |
| 124 |
# virtual_server = "inner-tunnel" |
| 125 |
#} |
| 126 |
|
| 127 |
|
| 128 |
# Cisco LEAP |
| 129 |
# |
| 130 |
# We do not recommend using LEAP in new deployments. See: |
| 131 |
# http://www.securiteam.com/tools/5TP012ACKE.html |
| 132 |
# |
| 133 |
# LEAP is not supported. |
| 134 |
# It is insecure, and no one should be using it. |
| 135 |
# |
| 136 |
|
| 137 |
|
| 138 |
# EAP-GTC -- Generic Token Card |
| 139 |
# |
| 140 |
# Currently, this is only permitted inside of EAP-TTLS, |
| 141 |
# or EAP-PEAP. The module "challenges" the user with |
| 142 |
# text, and the response from the user is taken to be |
| 143 |
# the User-Password. |
| 144 |
# |
| 145 |
# Proxying the tunneled EAP-GTC session is a bad idea, |
| 146 |
# the users password will go over the wire in plain-text, |
| 147 |
# for anyone to see. |
| 148 |
# |
| 149 |
gtc { |
| 150 |
# The default challenge, which many clients |
| 151 |
# ignore.. |
| 152 |
# |
| 153 |
# challenge = "Password: " |
| 154 |
|
| 155 |
# The plain-text response which comes back |
| 156 |
# is put into a User-Password attribute, |
| 157 |
# and passed to another module for |
| 158 |
# authentication. This allows the EAP-GTC |
| 159 |
# response to be checked against plain-text, |
| 160 |
# or crypt'd passwords. |
| 161 |
# |
| 162 |
# If you say "Local" instead of "PAP", then |
| 163 |
# the module will look for a User-Password |
| 164 |
# configured for the request, and do the |
| 165 |
# authentication itself. |
| 166 |
# |
| 167 |
auth_type = PAP |
| 168 |
} |
| 169 |
|
| 170 |
|
| 171 |
# Common TLS configuration for TLS-based EAP types |
| 172 |
# ------------------------------------------------ |
| 173 |
# |
| 174 |
# See raddb/certs/README.md for additional comments |
| 175 |
# on certificates. |
| 176 |
# |
| 177 |
# If OpenSSL was not found at the time the server was |
| 178 |
# built, the "tls", "ttls", and "peap" sections will |
| 179 |
# be ignored. |
| 180 |
# |
| 181 |
# If you do not currently have certificates signed by |
| 182 |
# a trusted CA you may use the 'snakeoil' certificates. |
| 183 |
# Included with the server in raddb/certs. |
| 184 |
# |
| 185 |
# If these certificates have not been auto-generated: |
| 186 |
# cd raddb/certs |
| 187 |
# make |
| 188 |
# |
| 189 |
# These test certificates SHOULD NOT be used in a normal |
| 190 |
# deployment. They are created only to make it easier |
| 191 |
# to install the server, and to perform some simple |
| 192 |
# tests with EAP-TLS, TTLS, or PEAP. |
| 193 |
# |
| 194 |
# Note that you should NOT use a globally known CA here! |
| 195 |
# e.g. using a Verisign cert as a "known CA" means that |
| 196 |
# ANYONE who has a certificate signed by them can |
| 197 |
# authenticate via EAP-TLS! This is likely not what you want. |
| 198 |
# |
| 199 |
tls-config tls-common { |
| 200 |
private_key_password = whatever |
| 201 |
private_key_file = /etc/ssl/private/ssl-cert-snakeoil.key |
| 202 |
|
| 203 |
# If Private key & Certificate are located in |
| 204 |
# the same file, then private_key_file & |
| 205 |
# certificate_file must contain the same file |
| 206 |
# name. |
| 207 |
# |
| 208 |
# If ca_file (below) is not used, then the |
| 209 |
# certificate_file below SHOULD also include all of |
| 210 |
# the intermediate CA certificates used to sign the |
| 211 |
# server certificate, but NOT the root CA. |
| 212 |
# |
| 213 |
# Including the ROOT CA certificate is not useful and |
| 214 |
# merely inflates the exchanged data volume during |
| 215 |
# the TLS negotiation. |
| 216 |
# |
| 217 |
# This file should contain the server certificate, |
| 218 |
# followed by intermediate certificates, in order. |
| 219 |
# i.e. If we have a server certificate signed by CA1, |
| 220 |
# which is signed by CA2, which is signed by a root |
| 221 |
# CA, then the "certificate_file" should contain |
| 222 |
# server.pem, followed by CA1.pem, followed by |
| 223 |
# CA2.pem. |
| 224 |
# |
| 225 |
# When using "ca_file" or "ca_path", the |
| 226 |
# "certificate_file" should contain only |
| 227 |
# "server.pem". And then you may (or may not) need |
| 228 |
# to set "auto_chain", depending on your version of |
| 229 |
# OpenSSL. |
| 230 |
# |
| 231 |
# In short, SSL / TLS certificates are complex. |
| 232 |
# There are many versions of software, each of which |
| 233 |
# behave slightly differently. It is impossible to |
| 234 |
# give advice which will work everywhere. Instead, |
| 235 |
# we give general guidelines. |
| 236 |
# |
| 237 |
certificate_file = /etc/ssl/certs/ssl-cert-snakeoil.pem |
| 238 |
|
| 239 |
# Trusted Root CA list |
| 240 |
# |
| 241 |
# This file can contain multiple CA certificates. |
| 242 |
# ALL of the CA's in this list will be trusted to |
| 243 |
# issue client certificates for authentication. |
| 244 |
# |
| 245 |
# In general, you should use self-signed |
| 246 |
# certificates for 802.1x (EAP) authentication. |
| 247 |
# In that case, this CA file should contain |
| 248 |
# *one* CA certificate. |
| 249 |
# |
| 250 |
ca_file = /etc/ssl/certs/ca-certificates.crt |
| 251 |
|
| 252 |
# |
| 253 |
# Directory where multiple CAs are stored. Both |
| 254 |
# "ca_file" and "ca_path" can be used at the same time. |
| 255 |
# |
| 256 |
# Each file in this directory must contain one |
| 257 |
# certificate, and ONLY one certificate. |
| 258 |
# |
| 259 |
ca_path = ${cadir} |
| 260 |
|
| 261 |
# OpenSSL does not reload contents of ca_path dir over time. |
| 262 |
# That means that if check_crl is enabled and CRLs are loaded |
| 263 |
# from ca_path dir, at some point CRLs will expire and |
| 264 |
# the server will stop authenticating users. |
| 265 |
# |
| 266 |
# If ca_path_reload_interval is non-zero, it will force OpenSSL |
| 267 |
# to reload all data from ca_path periodically |
| 268 |
# |
| 269 |
# Flush ca_path each hour |
| 270 |
# ca_path_reload_interval = 3600 |
| 271 |
|
| 272 |
# OpenSSL will automatically create certificate chains, |
| 273 |
# unless we tell it to not do that. The problem is that |
| 274 |
# it sometimes gets the chains right from a certificate |
| 275 |
# signature view, but wrong from the clients view. |
| 276 |
# |
| 277 |
# When setting "auto_chain = no", the server certificate |
| 278 |
# file MUST include the full certificate chain. |
| 279 |
# |
| 280 |
# auto_chain = yes |
| 281 |
|
| 282 |
# If OpenSSL supports TLS-PSK, then we can use a |
| 283 |
# fixed PSK identity and (hex) password. These can |
| 284 |
# be used at the same time as the certificate |
| 285 |
# configuration, but only for TLS 1.0 through 1.2. |
| 286 |
# |
| 287 |
# If PSK and certificates are configured at the same |
| 288 |
# time for TLS 1.3, then the server will warn you, |
| 289 |
# and will disable TLS 1.3, as it will not work. |
| 290 |
# |
| 291 |
# The work around is to have two modules (or for |
| 292 |
# RadSec, two listen sections). One will have PSK |
| 293 |
# configured, and the other will have certificates |
| 294 |
# configured. |
| 295 |
# |
| 296 |
# psk_identity = "test" |
| 297 |
# psk_hexphrase = "036363823" |
| 298 |
|
| 299 |
# Dynamic queries for the PSK. If TLS-PSK is used, |
| 300 |
# and psk_query is set, then you MUST NOT use |
| 301 |
# psk_identity or psk_hexphrase. |
| 302 |
# |
| 303 |
# Instead, use a dynamic expansion similar to the one |
| 304 |
# below. It keys off of TLS-PSK-Identity. It should |
| 305 |
# return a of string no more than 512 hex characters. |
| 306 |
# That string will be converted to binary, and will |
| 307 |
# be used as the dynamic PSK hexphrase. |
| 308 |
# |
| 309 |
# Note that this query is just an example. You will |
| 310 |
# need to customize it for your installation. |
| 311 |
# |
| 312 |
# psk_query = "%{sql:select hex(key) from psk_keys where keyid = '%{TLS-PSK-Identity}'}" |
| 313 |
|
| 314 |
# For DH cipher suites to work in OpenSSL < 1.1.0, |
| 315 |
# you have to run OpenSSL to create the DH file |
| 316 |
# first: |
| 317 |
# |
| 318 |
# openssl dhparam -out certs/dh 2048 |
| 319 |
# |
| 320 |
# For OpenSSL >= 1.1.0, just leave this commented |
| 321 |
# out, and OpenSSL will do the right thing. |
| 322 |
# |
| 323 |
# dh_file = ${certdir}/dh |
| 324 |
|
| 325 |
# If your system doesn't have /dev/urandom, |
| 326 |
# you will need to create this file, and |
| 327 |
# periodically change its contents. |
| 328 |
# |
| 329 |
# For security reasons, FreeRADIUS doesn't |
| 330 |
# write to files in its configuration |
| 331 |
# directory. |
| 332 |
# |
| 333 |
# random_file = /dev/urandom |
| 334 |
|
| 335 |
# This can never exceed the size of a RADIUS |
| 336 |
# packet (4096 bytes), and is preferably half |
| 337 |
# that, to accommodate other attributes in |
| 338 |
# RADIUS packet. On most APs the MAX packet |
| 339 |
# length is configured between 1500 - 1600 |
| 340 |
# In these cases, fragment size should be |
| 341 |
# 1024 or less. |
| 342 |
# |
| 343 |
# fragment_size = 1024 |
| 344 |
|
| 345 |
# include_length is a flag which is |
| 346 |
# by default set to yes If set to |
| 347 |
# yes, Total Length of the message is |
| 348 |
# included in EVERY packet we send. |
| 349 |
# If set to no, Total Length of the |
| 350 |
# message is included ONLY in the |
| 351 |
# First packet of a fragment series. |
| 352 |
# |
| 353 |
# include_length = yes |
| 354 |
|
| 355 |
|
| 356 |
# Check the Certificate Revocation List |
| 357 |
# |
| 358 |
# 1) Copy CA certificates and CRLs to same directory. |
| 359 |
# 2) Execute 'c_rehash <CA certs&CRLs Directory>'. |
| 360 |
# 'c_rehash' is OpenSSL's command. |
| 361 |
# 3) uncomment the lines below. |
| 362 |
# 5) Restart radiusd |
| 363 |
# check_crl = yes |
| 364 |
|
| 365 |
# Check if intermediate CAs have been revoked. |
| 366 |
# check_all_crl = yes |
| 367 |
|
| 368 |
# Accept an expired Certificate Revocation List |
| 369 |
# |
| 370 |
# allow_expired_crl = no |
| 371 |
|
| 372 |
# If check_cert_issuer is set, the value will |
| 373 |
# be checked against the DN of the issuer in |
| 374 |
# the client certificate. If the values do not |
| 375 |
# match, the certificate verification will fail, |
| 376 |
# rejecting the user. |
| 377 |
# |
| 378 |
# This check can be done more generally by checking |
| 379 |
# the value of the TLS-Client-Cert-Issuer attribute. |
| 380 |
# This check can be done via any mechanism you |
| 381 |
# choose. |
| 382 |
# |
| 383 |
# check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd" |
| 384 |
|
| 385 |
# If check_cert_cn is set, the value will |
| 386 |
# be xlat'ed and checked against the CN |
| 387 |
# in the client certificate. If the values |
| 388 |
# do not match, the certificate verification |
| 389 |
# will fail rejecting the user. |
| 390 |
# |
| 391 |
# This check is done only if the previous |
| 392 |
# "check_cert_issuer" is not set, or if |
| 393 |
# the check succeeds. |
| 394 |
# |
| 395 |
# This check can be done more generally by writing |
| 396 |
# "unlang" statements to examine the value of the |
| 397 |
# TLS-Client-Cert-Common-Name attribute. |
| 398 |
# |
| 399 |
# check_cert_cn = %{User-Name} |
| 400 |
|
| 401 |
# |
| 402 |
# This configuration item only applies when there is |
| 403 |
# an intermediate CA between the "root" CA, and the |
| 404 |
# client certificate. If we trust the root CA, then |
| 405 |
# by definition we also trust ANY intermediate CA |
| 406 |
# which is signed by that root. This means ANOTHER |
| 407 |
# intermediate CA can issue client certificates, and |
| 408 |
# have them accepted by the EAP module. |
| 409 |
# |
| 410 |
# The solution is to list ONLY the trusted CAs in the |
| 411 |
# FreeRADIUS configuration, and then set this |
| 412 |
# configuration item to "yes". |
| 413 |
# |
| 414 |
# Then, when the server receives a client certificate |
| 415 |
# from an untrusted CA, that authentication request |
| 416 |
# can be rejected. |
| 417 |
# |
| 418 |
# It is possible to do these checks in "unlang", by |
| 419 |
# checking for unknown names in the |
| 420 |
# TLS-Cert-Common-Name attribute, but that is |
| 421 |
# more complex. So we add a configuration option |
| 422 |
# which can be set once, and which works for all |
| 423 |
# possible intermediate CAs, no matter what their |
| 424 |
# value. |
| 425 |
# |
| 426 |
# reject_unknown_intermediate_ca = no |
| 427 |
|
| 428 |
# Set this option to specify the allowed |
| 429 |
# TLS cipher suites. The format is listed |
| 430 |
# in "man 1 ciphers". |
| 431 |
# |
| 432 |
cipher_list = "DEFAULT" |
| 433 |
|
| 434 |
# Set this option to specify the allowed |
| 435 |
# TLS signature algorithms for OpenSSL 1.1.1 and above. |
| 436 |
# The format and available signature algorithms are listed |
| 437 |
# in "man 3 SSL_CTX_set1_sigalgs_list". |
| 438 |
# |
| 439 |
# sigalgs_list = "" |
| 440 |
|
| 441 |
# If enabled, OpenSSL will use server cipher list |
| 442 |
# (possibly defined by cipher_list option above) |
| 443 |
# for choosing right cipher suite rather than |
| 444 |
# using client-specified list which is OpenSSl default |
| 445 |
# behavior. Setting this to "yes" means that OpenSSL |
| 446 |
# will choose the servers ciphers, even if they do not |
| 447 |
# best match what the client sends. |
| 448 |
# |
| 449 |
# TLS negotiation is usually good, but can be imperfect. |
| 450 |
# This setting allows administrators to "fine tune" it |
| 451 |
# if necessary. |
| 452 |
# |
| 453 |
cipher_server_preference = no |
| 454 |
|
| 455 |
# You can selectively disable TLS versions for |
| 456 |
# compatability with old client devices. |
| 457 |
# |
| 458 |
# If your system has OpenSSL 1.1.0 or greater, do NOT |
| 459 |
# use these. Instead, set tls_min_version and |
| 460 |
# tls_max_version. |
| 461 |
# |
| 462 |
# disable_tlsv1_2 = yes |
| 463 |
# disable_tlsv1_1 = yes |
| 464 |
# disable_tlsv1 = yes |
| 465 |
|
| 466 |
|
| 467 |
# Set min / max TLS version. |
| 468 |
# |
| 469 |
# Generally speaking you should NOT use TLS 1.0 or |
| 470 |
# TLS 1.1. They are old, possibly insecure, and |
| 471 |
# deprecated. However, it is sometimes necessary to |
| 472 |
# enable it for compatibility with legact systems. |
| 473 |
# We recommend replacing those legacy systems, and |
| 474 |
# using at least TLS 1.2. |
| 475 |
# |
| 476 |
# Some Debian versions disable older versions of TLS, |
| 477 |
# and requires the application to manually enable |
| 478 |
# them. |
| 479 |
# |
| 480 |
# If you are running such a distribution, you should |
| 481 |
# set these options, otherwise older clients will not |
| 482 |
# be able to connect. |
| 483 |
# |
| 484 |
# Allowed values are "1.0", "1.1", "1.2", and "1.3". |
| 485 |
# |
| 486 |
# As of 2021, it is STRONGLY RECOMMENDED to set |
| 487 |
# |
| 488 |
# tls_min_version = "1.2" |
| 489 |
# |
| 490 |
# Older TLS versions are insecure and deprecated. |
| 491 |
# |
| 492 |
# In order to enable TLS 1.0 and TLS 1.1, you may |
| 493 |
# also need to update cipher_list below to: |
| 494 |
# |
| 495 |
# * OpenSSL >= 3.x |
| 496 |
# |
| 497 |
# cipher_list = "DEFAULT@SECLEVEL=0" |
| 498 |
# |
| 499 |
# * OpenSSL < 3.x |
| 500 |
# |
| 501 |
# cipher_list = "DEFAULT@SECLEVEL=1" |
| 502 |
# |
| 503 |
# The values must be in quotes. |
| 504 |
# |
| 505 |
# We also STRONGLY RECOMMEND to set |
| 506 |
# |
| 507 |
# tls_max_version = "1.2" |
| 508 |
# |
| 509 |
# While the server will accept "1.3" as a value, |
| 510 |
# most EAP supplicants WILL NOT DO TLS 1.3 PROPERLY. |
| 511 |
# |
| 512 |
# i.e. they WILL NOT WORK, SO DO NOT ASK QUESTIONS ON |
| 513 |
# THE LIST ABOUT WHY IT DOES NOT WORK. |
| 514 |
# |
| 515 |
# The TLS 1.3 support is here for future |
| 516 |
# compatibility, as clients get upgraded, and people |
| 517 |
# don't upgrade their copies of FreeRADIUS. |
| 518 |
# |
| 519 |
# Also note that we only support TLS 1.3 for EAP-TLS, |
| 520 |
# TTLS, and PEAP. It is not supported for EAP-FAST. |
| 521 |
# |
| 522 |
tls_min_version = "1.2" |
| 523 |
tls_max_version = "1.2" |
| 524 |
|
| 525 |
# Elliptical cryptography configuration |
| 526 |
# |
| 527 |
# This configuration should be one of the following: |
| 528 |
# |
| 529 |
# * a name of the curve to use, e.g. "prime256v1". |
| 530 |
# |
| 531 |
# * a colon separated list of curve NIDs or names. |
| 532 |
# |
| 533 |
# * an empty string, in which case OpenSSL will choose |
| 534 |
# the "best" curve for the situation. |
| 535 |
# |
| 536 |
# For supported curve names, please run |
| 537 |
# |
| 538 |
# openssl ecparam -list_curves |
| 539 |
# |
| 540 |
ecdh_curve = "" |
| 541 |
|
| 542 |
# Session resumption / fast reauthentication |
| 543 |
# cache. |
| 544 |
# |
| 545 |
# The cache contains the following information: |
| 546 |
# |
| 547 |
# session Id - unique identifier, managed by SSL |
| 548 |
# User-Name - from the Access-Accept |
| 549 |
# Stripped-User-Name - from the Access-Request |
| 550 |
# Cached-Session-Policy - from the Access-Accept |
| 551 |
# |
| 552 |
# See also the "store" subsection below for |
| 553 |
# additional attributes which can be cached. |
| 554 |
# |
| 555 |
# The "Cached-Session-Policy" is the name of a |
| 556 |
# policy which should be applied to the cached |
| 557 |
# session. This policy can be used to assign |
| 558 |
# VLANs, IP addresses, etc. It serves as a useful |
| 559 |
# way to re-apply the policy from the original |
| 560 |
# Access-Accept to the subsequent Access-Accept |
| 561 |
# for the cached session. |
| 562 |
# |
| 563 |
# On session resumption, these attributes are |
| 564 |
# copied from the cache, and placed into the |
| 565 |
# reply list. |
| 566 |
# |
| 567 |
# You probably also want "use_tunneled_reply = yes" |
| 568 |
# when using fast session resumption. |
| 569 |
# |
| 570 |
# You can check if a session has been resumed by |
| 571 |
# looking for the existence of the EAP-Session-Resumed |
| 572 |
# attribute. Note that this attribute will *only* |
| 573 |
# exist in the "post-auth" section. |
| 574 |
# |
| 575 |
# CAVEATS: The cache is stored and reloaded BEFORE |
| 576 |
# the "post-auth" section is run. This limitation |
| 577 |
# makes caching more difficult than it should be. In |
| 578 |
# practice, it means that the first authentication |
| 579 |
# session must set the reply attributes before the |
| 580 |
# post-auth section is run. |
| 581 |
# |
| 582 |
# When the session is resumed, the attributes are |
| 583 |
# restored and placed into the session-state list. |
| 584 |
# |
| 585 |
cache { |
| 586 |
# Enable it. The default is "no". Deleting the entire "cache" |
| 587 |
# subsection also disables caching. |
| 588 |
# |
| 589 |
# The session cache requires the use of the |
| 590 |
# "name" and "persist_dir" configuration |
| 591 |
# items, below. |
| 592 |
# |
| 593 |
# The internal OpenSSL session cache has been permanently |
| 594 |
# disabled. |
| 595 |
# |
| 596 |
# You can disallow resumption for a particular user by adding the |
| 597 |
# following attribute to the control item list: |
| 598 |
# |
| 599 |
# Allow-Session-Resumption = No |
| 600 |
# |
| 601 |
# If "enable = no" below, you CANNOT enable resumption for just one |
| 602 |
# user by setting the above attribute to "yes". |
| 603 |
# |
| 604 |
enable = no |
| 605 |
|
| 606 |
# Lifetime of the cached entries, in hours. The sessions will be |
| 607 |
# deleted/invalidated after this time. |
| 608 |
# |
| 609 |
lifetime = 24 # hours |
| 610 |
|
| 611 |
# Internal "name" of the session cache. Used to |
| 612 |
# distinguish which TLS context sessions belong to. |
| 613 |
# |
| 614 |
# The server will generate a random value if unset. |
| 615 |
# This will change across server restart so you MUST |
| 616 |
# set the "name" if you want to persist sessions (see |
| 617 |
# below). |
| 618 |
# |
| 619 |
# name = "EAP module" |
| 620 |
|
| 621 |
# Simple directory-based storage of sessions. |
| 622 |
# Two files per session will be written, the SSL |
| 623 |
# state and the cached VPs. This will persist session |
| 624 |
# across server restarts. |
| 625 |
# |
| 626 |
# The default directory is ${logdir}, for historical |
| 627 |
# reasons. You should ${db_dir} instead. And check |
| 628 |
# the value of db_dir in the main radiusd.conf file. |
| 629 |
# It should not point to ${raddb} |
| 630 |
# |
| 631 |
# The server will need write perms, and the directory |
| 632 |
# should be secured from anyone else. You might want |
| 633 |
# a script to remove old files from here periodically: |
| 634 |
# |
| 635 |
# find ${logdir}/tlscache -mtime +2 -exec rm -f {} \; |
| 636 |
# |
| 637 |
# This feature REQUIRES "name" option be set above. |
| 638 |
# |
| 639 |
# persist_dir = "${logdir}/tlscache" |
| 640 |
|
| 641 |
# |
| 642 |
# It is possible to partially |
| 643 |
# control which attributes exist in the |
| 644 |
# session cache. This subsection lists |
| 645 |
# attributes which are taken from the reply, |
| 646 |
# and saved to the on-disk cache. When the |
| 647 |
# session is resumed, these attributes are |
| 648 |
# added to the "session-state" list. The |
| 649 |
# default configuration will then take care |
| 650 |
# of copying them to the reply. |
| 651 |
# |
| 652 |
store { |
| 653 |
Tunnel-Private-Group-Id |
| 654 |
} |
| 655 |
} |
| 656 |
|
| 657 |
# Client certificates can be validated via an |
| 658 |
# external command. This allows dynamic CRLs or OCSP |
| 659 |
# to be used. |
| 660 |
# |
| 661 |
# This configuration is commented out in the |
| 662 |
# default configuration. Uncomment it, and configure |
| 663 |
# the correct paths below to enable it. |
| 664 |
# |
| 665 |
# If OCSP checking is enabled, and the OCSP checks fail, |
| 666 |
# the verify section is not run. |
| 667 |
# |
| 668 |
# If OCSP checking is disabled, the verify section is |
| 669 |
# run on successful certificate validation. |
| 670 |
# |
| 671 |
verify { |
| 672 |
# If the OCSP checks succeed, the verify section |
| 673 |
# is run to allow additional checks. |
| 674 |
# |
| 675 |
# If you want to skip verify on OCSP success, |
| 676 |
# uncomment this configuration item, and set it |
| 677 |
# to "yes". |
| 678 |
# |
| 679 |
# skip_if_ocsp_ok = no |
| 680 |
|
| 681 |
# A temporary directory where the client |
| 682 |
# certificates are stored. This directory |
| 683 |
# MUST be owned by the UID of the server, |
| 684 |
# and MUST not be accessible by any other |
| 685 |
# users. When the server starts, it will do |
| 686 |
# "chmod go-rwx" on the directory, for |
| 687 |
# security reasons. The directory MUST |
| 688 |
# exist when the server starts. |
| 689 |
# |
| 690 |
# You should also delete all of the files |
| 691 |
# in the directory when the server starts. |
| 692 |
# |
| 693 |
# Note that, on Linux systems with systemd, the |
| 694 |
# /tmp directory may be restricted. In this case |
| 695 |
# it may be best to use `${run_dir}/tmp` here |
| 696 |
# and create the temporary directory with the |
| 697 |
# systemd `RuntimeDirectory` unit option. |
| 698 |
# |
| 699 |
# tmpdir = /tmp/radiusd |
| 700 |
|
| 701 |
# The command used to verify the client cert. |
| 702 |
# We recommend using the OpenSSL command-line |
| 703 |
# tool. |
| 704 |
# |
| 705 |
# The ${..ca_path} text is a reference to |
| 706 |
# the ca_path variable defined above. |
| 707 |
# |
| 708 |
# The %{TLS-Client-Cert-Filename} is the name |
| 709 |
# of the temporary file containing the cert |
| 710 |
# in PEM format. This file is automatically |
| 711 |
# deleted by the server when the command |
| 712 |
# returns. |
| 713 |
# |
| 714 |
# client = "/path/to/openssl verify -CApath ${..ca_path} %{TLS-Client-Cert-Filename}" |
| 715 |
} |
| 716 |
|
| 717 |
# OCSP Configuration |
| 718 |
# |
| 719 |
# Certificates can be verified against an OCSP |
| 720 |
# Responder. This makes it possible to immediately |
| 721 |
# revoke certificates without the distribution of |
| 722 |
# new Certificate Revocation Lists (CRLs). |
| 723 |
# |
| 724 |
ocsp { |
| 725 |
# Enable it. The default is "no". |
| 726 |
# Deleting the entire "ocsp" subsection |
| 727 |
# also disables ocsp checking |
| 728 |
# |
| 729 |
enable = no |
| 730 |
|
| 731 |
# The OCSP Responder URL can be automatically |
| 732 |
# extracted from the certificate in question. |
| 733 |
# To override the OCSP Responder URL set |
| 734 |
# "override_cert_url = yes". |
| 735 |
# |
| 736 |
override_cert_url = yes |
| 737 |
|
| 738 |
# If the OCSP Responder address is not extracted from |
| 739 |
# the certificate, the URL can be defined here. |
| 740 |
# |
| 741 |
url = "http://127.0.0.1/ocsp/" |
| 742 |
|
| 743 |
# If the OCSP Responder can not cope with nonce |
| 744 |
# in the request, then it can be disabled here. |
| 745 |
# |
| 746 |
# For security reasons, disabling this option |
| 747 |
# is not recommended as nonce protects against |
| 748 |
# replay attacks. |
| 749 |
# |
| 750 |
# Note that Microsoft AD Certificate Services OCSP |
| 751 |
# Responder does not enable nonce by default. It is |
| 752 |
# more secure to enable nonce on the responder than |
| 753 |
# to disable it in the query here. |
| 754 |
# See http://technet.microsoft.com/en-us/library/cc770413%28WS.10%29.aspx |
| 755 |
# |
| 756 |
# use_nonce = yes |
| 757 |
|
| 758 |
# Number of seconds before giving up waiting |
| 759 |
# for OCSP response. 0 uses system default. |
| 760 |
# |
| 761 |
# timeout = 0 |
| 762 |
|
| 763 |
# Normally an error in querying the OCSP |
| 764 |
# responder (no response from server, server did |
| 765 |
# not understand the request, etc) will result in |
| 766 |
# a validation failure. |
| 767 |
# |
| 768 |
# To treat these errors as 'soft' failures and |
| 769 |
# still accept the certificate, enable this |
| 770 |
# option. |
| 771 |
# |
| 772 |
# Warning: this may enable clients with revoked |
| 773 |
# certificates to connect if the OCSP responder |
| 774 |
# is not available. Use with caution. |
| 775 |
# |
| 776 |
# softfail = no |
| 777 |
} |
| 778 |
|
| 779 |
# |
| 780 |
# The server can present different certificates based |
| 781 |
# on the realm presented in EAP. See |
| 782 |
# raddb/certs/realms/README.md for examples of how to |
| 783 |
# configure this. |
| 784 |
# |
| 785 |
# Note that the default is to use the same set of |
| 786 |
# realm certificates for both EAP and RadSec! If |
| 787 |
# this is not what you want, you should use different |
| 788 |
# subdirectories or each, e.g. ${certdir}/realms/radsec/, |
| 789 |
# and ${certdir}/realms/eap/ |
| 790 |
# |
| 791 |
# realm_dir = ${certdir}/realms/ |
| 792 |
} |
| 793 |
|
| 794 |
|
| 795 |
# EAP-TLS |
| 796 |
# |
| 797 |
# The TLS configuration for TLS-based EAP types is held in |
| 798 |
# the "tls-config" section, above. |
| 799 |
# |
| 800 |
tls { |
| 801 |
# Point to the common TLS configuration |
| 802 |
# |
| 803 |
tls = tls-common |
| 804 |
|
| 805 |
# As part of checking a client certificate, the EAP-TLS |
| 806 |
# sets some attributes such as TLS-Client-Cert-Common-Name. This |
| 807 |
# virtual server has access to these attributes, and can |
| 808 |
# be used to accept or reject the request. |
| 809 |
# |
| 810 |
# virtual_server = check-eap-tls |
| 811 |
|
| 812 |
# You can control whether or not EAP-TLS requires a |
| 813 |
# client certificate by setting |
| 814 |
# |
| 815 |
# configurable_client_cert = yes |
| 816 |
# |
| 817 |
# Once that setting has been changed, you can then set |
| 818 |
# |
| 819 |
# EAP-TLS-Require-Client-Cert = No |
| 820 |
# |
| 821 |
# in the control items for a request, and the EAP-TLS |
| 822 |
# module will not require a client certificate from |
| 823 |
# the supplicant. |
| 824 |
# |
| 825 |
# WARNING: This configuration should only be used |
| 826 |
# when the users are placed into a "captive portal" |
| 827 |
# or "walled garden", where they have limited network |
| 828 |
# access. Otherwise the configuration will allow |
| 829 |
# anyone on the network, without authenticating them! |
| 830 |
# |
| 831 |
# configurable_client_cert = no |
| 832 |
} |
| 833 |
|
| 834 |
|
| 835 |
# EAP-TTLS -- Tunneled TLS |
| 836 |
# |
| 837 |
# The TTLS module implements the EAP-TTLS protocol, |
| 838 |
# which can be described as EAP inside of Diameter, |
| 839 |
# inside of TLS, inside of EAP, inside of RADIUS... |
| 840 |
# |
| 841 |
# Surprisingly, it works quite well. |
| 842 |
# |
| 843 |
ttls { |
| 844 |
# Which tls-config section the TLS negotiation parameters |
| 845 |
# are in - see EAP-TLS above for an explanation. |
| 846 |
# |
| 847 |
# In the case that an old configuration from FreeRADIUS |
| 848 |
# v2.x is being used, all the options of the tls-config |
| 849 |
# section may also appear instead in the 'tls' section |
| 850 |
# above. If that is done, the tls= option here (and in |
| 851 |
# tls above) MUST be commented out. |
| 852 |
# |
| 853 |
tls = tls-common |
| 854 |
|
| 855 |
# The tunneled EAP session needs a default EAP type |
| 856 |
# which is separate from the one for the non-tunneled |
| 857 |
# EAP module. Inside of the TTLS tunnel, we recommend |
| 858 |
# using EAP-MD5. If the request does not contain an |
| 859 |
# EAP conversation, then this configuration entry is |
| 860 |
# ignored. |
| 861 |
# |
| 862 |
default_eap_type = md5 |
| 863 |
|
| 864 |
# The tunneled authentication request does not usually |
| 865 |
# contain useful attributes like 'Calling-Station-Id', |
| 866 |
# etc. These attributes are outside of the tunnel, |
| 867 |
# and normally unavailable to the tunneled |
| 868 |
# authentication request. |
| 869 |
# |
| 870 |
# By setting this configuration entry to 'yes', |
| 871 |
# any attribute which is NOT in the tunneled |
| 872 |
# authentication request, but which IS available |
| 873 |
# outside of the tunnel, is copied to the tunneled |
| 874 |
# request. |
| 875 |
# |
| 876 |
# allowed values: {no, yes} |
| 877 |
# |
| 878 |
copy_request_to_tunnel = no |
| 879 |
|
| 880 |
# This configuration item is deprecated. Instead, |
| 881 |
# you should use: |
| 882 |
# |
| 883 |
# update outer.session-state { |
| 884 |
# ... |
| 885 |
# } |
| 886 |
# |
| 887 |
# This will cache attributes for the final Access-Accept. |
| 888 |
# |
| 889 |
# See "update outer.session-state" in the "post-auth" |
| 890 |
# sections of sites-available/default, and of |
| 891 |
# sites-available/inner-tunnel |
| 892 |
# |
| 893 |
# The reply attributes sent to the NAS are usually |
| 894 |
# based on the name of the user 'outside' of the |
| 895 |
# tunnel (usually 'anonymous'). If you want to send |
| 896 |
# the reply attributes based on the user name inside |
| 897 |
# of the tunnel, then set this configuration entry to |
| 898 |
# 'yes', and the reply to the NAS will be taken from |
| 899 |
# the reply to the tunneled request. |
| 900 |
# |
| 901 |
# allowed values: {no, yes} |
| 902 |
# |
| 903 |
use_tunneled_reply = no |
| 904 |
|
| 905 |
# The inner tunneled request can be sent |
| 906 |
# through a virtual server constructed |
| 907 |
# specifically for this purpose. |
| 908 |
# |
| 909 |
# A virtual server MUST be specified. |
| 910 |
# |
| 911 |
virtual_server = "inner-tunnel" |
| 912 |
|
| 913 |
# This has the same meaning, and overwrites, the |
| 914 |
# same field in the "tls" configuration, above. |
| 915 |
# The default value here is "yes". |
| 916 |
# |
| 917 |
# include_length = yes |
| 918 |
|
| 919 |
# Unlike EAP-TLS, EAP-TTLS does not require a client |
| 920 |
# certificate. However, you can require one by setting the |
| 921 |
# following option. You can also override this option by |
| 922 |
# setting |
| 923 |
# |
| 924 |
# EAP-TLS-Require-Client-Cert = Yes |
| 925 |
# |
| 926 |
# in the control items for a request. |
| 927 |
# |
| 928 |
# Note that the majority of supplicants do not support using a |
| 929 |
# client certificate with EAP-TTLS, so this option is unlikely |
| 930 |
# to be usable for most people. |
| 931 |
# |
| 932 |
# require_client_cert = yes |
| 933 |
} |
| 934 |
|
| 935 |
|
| 936 |
# EAP-PEAP |
| 937 |
# |
| 938 |
|
| 939 |
################################################## |
| 940 |
# |
| 941 |
# !!!!! WARNINGS for Windows compatibility !!!!! |
| 942 |
# |
| 943 |
################################################## |
| 944 |
# |
| 945 |
# If you see the server send an Access-Challenge, |
| 946 |
# and the client never sends another Access-Request, |
| 947 |
# then |
| 948 |
# |
| 949 |
# STOP! |
| 950 |
# |
| 951 |
# The server certificate has to have special OID's |
| 952 |
# in it, or else the Microsoft clients will silently |
| 953 |
# fail. See the "scripts/xpextensions" file for |
| 954 |
# details, and the following page: |
| 955 |
# |
| 956 |
# https://support.microsoft.com/en-us/help/814394/ |
| 957 |
# |
| 958 |
# If is still doesn't work, and you're using Samba, |
| 959 |
# you may be encountering a Samba bug. See: |
| 960 |
# |
| 961 |
# https://bugzilla.samba.org/show_bug.cgi?id=6563 |
| 962 |
# |
| 963 |
# Note that we do not necessarily agree with their |
| 964 |
# explanation... but the fix does appear to work. |
| 965 |
# |
| 966 |
################################################## |
| 967 |
|
| 968 |
# The tunneled EAP session needs a default EAP type |
| 969 |
# which is separate from the one for the non-tunneled |
| 970 |
# EAP module. Inside of the TLS/PEAP tunnel, we |
| 971 |
# recommend using EAP-MS-CHAPv2. |
| 972 |
# |
| 973 |
peap { |
| 974 |
# Which tls-config section the TLS negotiation parameters |
| 975 |
# are in - see EAP-TLS above for an explanation. |
| 976 |
# |
| 977 |
# In the case that an old configuration from FreeRADIUS |
| 978 |
# v2.x is being used, all the options of the tls-config |
| 979 |
# section may also appear instead in the 'tls' section |
| 980 |
# above. If that is done, the tls= option here (and in |
| 981 |
# tls above) MUST be commented out. |
| 982 |
# |
| 983 |
tls = tls-common |
| 984 |
|
| 985 |
# The tunneled EAP session needs a default |
| 986 |
# EAP type which is separate from the one for |
| 987 |
# the non-tunneled EAP module. Inside of the |
| 988 |
# PEAP tunnel, we recommend using MS-CHAPv2, |
| 989 |
# as that is the default type supported by |
| 990 |
# Windows clients. |
| 991 |
# |
| 992 |
default_eap_type = mschapv2 |
| 993 |
|
| 994 |
# The PEAP module also has these configuration |
| 995 |
# items, which are the same as for TTLS. |
| 996 |
# |
| 997 |
copy_request_to_tunnel = no |
| 998 |
|
| 999 |
# This configuration item is deprecated. Instead, |
| 1000 |
# you should use: |
| 1001 |
# |
| 1002 |
# update outer.session-state { |
| 1003 |
# ... |
| 1004 |
# } |
| 1005 |
# |
| 1006 |
# This will cache attributes for the final Access-Accept. |
| 1007 |
# |
| 1008 |
# See "update outer.session-state" in the "post-auth" |
| 1009 |
# sections of sites-available/default, and of |
| 1010 |
# sites-available/inner-tunnel |
| 1011 |
# |
| 1012 |
use_tunneled_reply = no |
| 1013 |
|
| 1014 |
# When the tunneled session is proxied, the |
| 1015 |
# home server may not understand EAP-MSCHAP-V2. |
| 1016 |
# Set this entry to "no" to proxy the tunneled |
| 1017 |
# EAP-MSCHAP-V2 as normal MSCHAPv2. |
| 1018 |
# |
| 1019 |
# This setting can be over-ridden on a packet by |
| 1020 |
# packet basis by setting |
| 1021 |
# |
| 1022 |
# &control:Proxy-Tunneled-Request-As-EAP = yes |
| 1023 |
# |
| 1024 |
# proxy_tunneled_request_as_eap = yes |
| 1025 |
|
| 1026 |
# The inner tunneled request can be sent |
| 1027 |
# through a virtual server constructed |
| 1028 |
# specifically for this purpose. |
| 1029 |
# |
| 1030 |
# A virtual server MUST be specified. |
| 1031 |
# |
| 1032 |
virtual_server = "inner-tunnel" |
| 1033 |
|
| 1034 |
# This option enables support for MS-SoH |
| 1035 |
# see doc/SoH.txt for more info. |
| 1036 |
# It is disabled by default. |
| 1037 |
# |
| 1038 |
# soh = yes |
| 1039 |
|
| 1040 |
# The SoH reply will be turned into a request which |
| 1041 |
# can be sent to a specific virtual server: |
| 1042 |
# |
| 1043 |
# soh_virtual_server = "soh-server" |
| 1044 |
|
| 1045 |
# Unlike EAP-TLS, PEAP does not require a client certificate. |
| 1046 |
# However, you can require one by setting the following |
| 1047 |
# option. You can also override this option by setting |
| 1048 |
# |
| 1049 |
# EAP-TLS-Require-Client-Cert = Yes |
| 1050 |
# |
| 1051 |
# in the control items for a request. |
| 1052 |
# |
| 1053 |
# Note that the majority of supplicants do not support using a |
| 1054 |
# client certificate with PEAP, so this option is unlikely to |
| 1055 |
# be usable for most people. |
| 1056 |
# |
| 1057 |
# require_client_cert = yes |
| 1058 |
} |
| 1059 |
|
| 1060 |
|
| 1061 |
# EAP-MSCHAPv2 |
| 1062 |
# |
| 1063 |
# Note that it is the EAP MS-CHAPv2 sub-module, not |
| 1064 |
# the main 'mschap' module. |
| 1065 |
# |
| 1066 |
# Note also that in order for this sub-module to work, |
| 1067 |
# the main 'mschap' module MUST ALSO be configured. |
| 1068 |
# |
| 1069 |
# This module is the *Microsoft* implementation of MS-CHAPv2 |
| 1070 |
# in EAP. There is another (incompatible) implementation |
| 1071 |
# of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not |
| 1072 |
# currently support. |
| 1073 |
# |
| 1074 |
mschapv2 { |
| 1075 |
# In earlier versions of the server, this module |
| 1076 |
# never sent the MS-CHAP-Error message to the client. |
| 1077 |
# This worked, but it had issues when the cached |
| 1078 |
# password was wrong. The server *should* send |
| 1079 |
# "E=691 R=0" to the client, which tells it to prompt |
| 1080 |
# the user for a new password. |
| 1081 |
# |
| 1082 |
# The default is to use that functionality. which is |
| 1083 |
# known to work. If you set "send_error = yes", then |
| 1084 |
# the error message will be sent back to the client. |
| 1085 |
# This *may* help some clients work better, but *may* |
| 1086 |
# also cause other clients to stop working. |
| 1087 |
# |
| 1088 |
# send_error = no |
| 1089 |
|
| 1090 |
# Server identifier to send back in the challenge. |
| 1091 |
# This should generally be the host name of the |
| 1092 |
# RADIUS server. Or, some information to uniquely |
| 1093 |
# identify it. |
| 1094 |
# |
| 1095 |
# identity = "FreeRADIUS" |
| 1096 |
} |
| 1097 |
|
| 1098 |
|
| 1099 |
# EAP-FAST |
| 1100 |
# |
| 1101 |
# The FAST module implements the EAP-FAST protocol |
| 1102 |
# |
| 1103 |
#fast { |
| 1104 |
# Point to the common TLS configuration |
| 1105 |
# |
| 1106 |
# tls = tls-common |
| 1107 |
|
| 1108 |
# If 'cipher_list' is set here, it will over-ride the |
| 1109 |
# 'cipher_list' configuration from the 'tls-common' |
| 1110 |
# configuration. The EAP-FAST module has it's own |
| 1111 |
# over-ride for 'cipher_list' because the |
| 1112 |
# specifications mandate a different set of ciphers |
| 1113 |
# than are used by the other EAP methods. |
| 1114 |
# |
| 1115 |
# cipher_list though must include "ADH" for anonymous provisioning. |
| 1116 |
# This is not as straight forward as appending "ADH" alongside |
| 1117 |
# "DEFAULT" as "DEFAULT" contains "!aNULL" so instead it is |
| 1118 |
# recommended "ALL:!EXPORT:!eNULL:!SSLv2" is used |
| 1119 |
# |
| 1120 |
# cipher_list = "ALL:!EXPORT:!eNULL:!SSLv2" |
| 1121 |
|
| 1122 |
# PAC lifetime in seconds (default: seven days) |
| 1123 |
# |
| 1124 |
# pac_lifetime = 604800 |
| 1125 |
|
| 1126 |
# Authority ID of the server |
| 1127 |
# |
| 1128 |
# If you are running a cluster of RADIUS servers, you should make |
| 1129 |
# the value chosen here (and for "pac_opaque_key") the same on all |
| 1130 |
# your RADIUS servers. This value should be unique to your |
| 1131 |
# installation. We suggest using a domain name. |
| 1132 |
# |
| 1133 |
# authority_identity = "1234" |
| 1134 |
|
| 1135 |
# PAC Opaque encryption key (must be exactly 32 bytes in size) |
| 1136 |
# |
| 1137 |
# This value MUST be secret, and MUST be generated using |
| 1138 |
# a secure method, such as via 'openssl rand -hex 32' |
| 1139 |
# |
| 1140 |
# pac_opaque_key = "0123456789abcdef0123456789ABCDEF" |
| 1141 |
|
| 1142 |
# Same as for TTLS, PEAP, etc. |
| 1143 |
# |
| 1144 |
# virtual_server = inner-tunnel |
| 1145 |
#} |
| 1146 |
|
| 1147 |
# EAP-TEAP |
| 1148 |
# |
| 1149 |
# The TEAP module implements the EAP-TEAP protocol |
| 1150 |
# |
| 1151 |
# #### Notes regarding Microsoft Windows 11 #### |
| 1152 |
# |
| 1153 |
# The Windows supplicant is *extremely* temperamental, |
| 1154 |
# seemingly across all EAP methods but especially so for |
| 1155 |
# TEAP. For example, for TLS 1.3, it supports session |
| 1156 |
# resumption with EAP-TLS, but not with PEAP or TTLS. This |
| 1157 |
# issue has been raised with Microsoft, but has not yet been |
| 1158 |
# addressed. |
| 1159 |
# |
| 1160 |
# We cannot help you with configuring Windows, other than to |
| 1161 |
# provide an account of our observations with a stock, |
| 1162 |
# non-updated Windows 11 25H2 install with the usual caveat |
| 1163 |
# "your mileage may vary". |
| 1164 |
# |
| 1165 |
# The observations below describe how to configure Microsoft |
| 1166 |
# Windows 11 and FreeRADIUS. If you don't follow similar |
| 1167 |
# steps, then TEAP is unlikely to work. |
| 1168 |
# |
| 1169 |
# * We found the new style 802.1X UI is unusable and you should |
| 1170 |
# use the old UI; found by searching for 'View network connections' |
| 1171 |
# using the search bar, right clicking on your network interface, |
| 1172 |
# selecting 'Properties' and then go to the 'Authentication' tab. |
| 1173 |
# |
| 1174 |
# * You are not able to configure the supplicant to skip |
| 1175 |
# verifying the CA or server name, both of those |
| 1176 |
# verification steps should be configured. |
| 1177 |
# |
| 1178 |
# * Due to a bug known to Microsoft since 2022, when using wired |
| 1179 |
# 802.1X you may find no traffic is sent to the RADIUS server, |
| 1180 |
# this can be resolved by disabling and re-enabling the interface. |
| 1181 |
# |
| 1182 |
# * 'machine' authentication is ALWAYS EAP-TLS; if you set EAP-MSCHAPv2 |
| 1183 |
# the authentication starts, but the identity used is for the machine |
| 1184 |
# whilst the credentials come from some non-interactive process. |
| 1185 |
# |
| 1186 |
# * 'user' authentication is almost always EAP-MSCHAPv2 or if EAP-TLS |
| 1187 |
# then a 'smartcard'; which can (in theory) be Windows Hello. |
| 1188 |
# |
| 1189 |
# * For user-based authentication, the 'Sign in' button may |
| 1190 |
# not appear or stop functioning resulting in no further |
| 1191 |
# RADIUS traffic. The workaround we found was to close |
| 1192 |
# completely the new UI page and let the 'Sign in' toast |
| 1193 |
# popup open the UI. |
| 1194 |
# |
| 1195 |
# Failing the above, make sure you have checked 'Fall-back |
| 1196 |
# to unauthorized network access', otherwise you may never |
| 1197 |
# see the 'Sign in' button or toast popup window to enter |
| 1198 |
# credentials; as such we recommend you leave this setting |
| 1199 |
# enabled. |
| 1200 |
# |
| 1201 |
# * Interactive authentications (such as EAP-MSCHAPv2) can lead to |
| 1202 |
# the credentials prompt, but after providing your credentials |
| 1203 |
# Windows does not send them to your RADIUS server. If this |
| 1204 |
# happens, disable and re-enable your network interface. |
| 1205 |
# |
| 1206 |
# * If you wish to use both EAP-TLS for machine and user authentication |
| 1207 |
# you will need to configure one of the methods to use a Smartcard. |
| 1208 |
# |
| 1209 |
# - Attempting to use an installed client certificate seemingly |
| 1210 |
# stalls from the perspective of the user. However, the RADIUS |
| 1211 |
# server receives a non-standard empty EAP identity and therefore |
| 1212 |
# can only respond with an Access-Reject. |
| 1213 |
# |
| 1214 |
# That is, when Windows has no crentials it doesn't send |
| 1215 |
# a TEAP error, it just starts EAP with no identity. |
| 1216 |
# This behavior violates the base EAP specifications, |
| 1217 |
# and also the TEAP specfication. |
| 1218 |
# |
| 1219 |
# - After selecting the Smartcard identity to use, |
| 1220 |
# Windows may immediately claim authentication failed. |
| 1221 |
# However, it has sent no traffic to the RADIUS |
| 1222 |
# server. To resolve this, re-insert your Smartcard. |
| 1223 |
# |
| 1224 |
# - We have only tested this using QEMU's CCID emulation |
| 1225 |
# and with the Smartcard functionality in UNIX 'spicy' |
| 1226 |
# client. Your mileage may vary. |
| 1227 |
# |
| 1228 |
# * The configuration of the methods used must match the value you |
| 1229 |
# set in 'identity_types', below. |
| 1230 |
# |
| 1231 |
# If you use 'none' as the secondary method then you must set |
| 1232 |
# 'identity_types' to a single value; using optional methods |
| 1233 |
# for 'identity_types' will lead to an authentication failure |
| 1234 |
# as Windows will send to the RADIUS server with Unexpected-TLVs |
| 1235 |
# |
| 1236 |
# For Windows, though the language 'primary' and 'secondary' |
| 1237 |
# imply preference, the implementation is in fact ordering based. |
| 1238 |
# |
| 1239 |
# You must configure Windows in the same order of methods |
| 1240 |
# that you set in 'identity_types' and also the values you |
| 1241 |
# use for machine_eap_type and user_eap_type. |
| 1242 |
# |
| 1243 |
# * The value used for 'Specify authentication mode' (which |
| 1244 |
# is found under 'Additional settings') must be set |
| 1245 |
# correctly for the value of 'identity_types' you want to |
| 1246 |
# use below: |
| 1247 |
# |
| 1248 |
# - unchecked leads to automatic detection and selection |
| 1249 |
# of one of the following settings. Windows often |
| 1250 |
# incorrectly selects something you do not desire, |
| 1251 |
# especially when optional methods are in use. |
| 1252 |
# |
| 1253 |
# - Windows "User or computer authentication": |
| 1254 |
# |
| 1255 |
# * Supports FreeRADIUS 'identity_types = machine,user' |
| 1256 |
# and 'identity_types = user,machine' |
| 1257 |
# |
| 1258 |
# - Windows "Computer authentication" |
| 1259 |
# |
| 1260 |
# * Supports FreeRADIUS 'identity_types = machine' |
| 1261 |
# |
| 1262 |
# * Supports FreeRADIUS 'identity_types = machine,?user', |
| 1263 |
# if you have a dummy EAP-MSCHAPv2 |
| 1264 |
# secondary method configured on Windows |
| 1265 |
# |
| 1266 |
# * Does not support FreeRADIUS 'identity_types = ?user,machine' |
| 1267 |
# |
| 1268 |
# - Windows "User authentication" |
| 1269 |
# |
| 1270 |
# * Supports FreeRADIUS 'identity_types = user' |
| 1271 |
# |
| 1272 |
# * Supports FreeRADIUS 'identity_types = user,?machine', |
| 1273 |
# if you have a dummy EAP-TLS secondary method |
| 1274 |
# configured on Windows |
| 1275 |
# |
| 1276 |
# * Does not support FreeRADIUS 'identity_types = ?machine,user' |
| 1277 |
# |
| 1278 |
# - Windows "Guest authentication" |
| 1279 |
# |
| 1280 |
# * Unsupported (we assume that Windows uses this to |
| 1281 |
# mean use "no inner methods") as it Windows sends a |
| 1282 |
# non-compliant zero length EAP-Identity before TEAP |
| 1283 |
# is even negotiated. |
| 1284 |
# |
| 1285 |
# * EAP-TLS followed by either EAP-TLS or EAP-MSCHAPv2 is supported |
| 1286 |
# |
| 1287 |
# - EAP-MSCHAPv2 followed by EAP-TLS is unsupported. See |
| 1288 |
# RFC 9930, sections 5.1 and 6.2.5. Using this method |
| 1289 |
# can lead to Tunnel-Compromise. |
| 1290 |
# |
| 1291 |
# * When selecting the 'primary' and 'secondary' EAP |
| 1292 |
# methods in Windows, they must match your configuration |
| 1293 |
# here for 'user_eap_type' and 'machine_eap_type' with the |
| 1294 |
# constraint: |
| 1295 |
# |
| 1296 |
# - 'machine' can be EAP-TLS with a Windows configuration of |
| 1297 |
# 'Use a certificate on this computer' |
| 1298 |
# |
| 1299 |
# - 'user' may be EAP-MSCHAPV2 or EAP-TLS with a Windows |
| 1300 |
# configuration of 'Use my smart card' |
| 1301 |
# |
| 1302 |
# * It may be possible to use Windows Hello here to provide |
| 1303 |
# a non-smartcard EAP-TLS (ie. TPM) secured certificate |
| 1304 |
# |
| 1305 |
# In short, TEAP is functional in a very, very limited set of |
| 1306 |
# situations. The FreeRADIUS team is working in the IETF on |
| 1307 |
# TEAPv2 which will address this, and other issues with TEAP. |
| 1308 |
# |
| 1309 |
# ############################################## |
| 1310 |
# |
| 1311 |
#teap { |
| 1312 |
# Point to the common TLS configuration |
| 1313 |
# |
| 1314 |
# tls = tls-common |
| 1315 |
|
| 1316 |
# |
| 1317 |
# Define which inner authentications are allowed, and |
| 1318 |
# in what order. |
| 1319 |
# |
| 1320 |
# allowed values: "machine,user" |
| 1321 |
# "user,machine" |
| 1322 |
# "user" |
| 1323 |
# "machine" |
| 1324 |
# |
| 1325 |
# If only one method is listed, then that is the only |
| 1326 |
# method which is allowed. The server will reject |
| 1327 |
# authentication if the defined method isn't |
| 1328 |
# provided. |
| 1329 |
# |
| 1330 |
# If only one method is listed, then the server will |
| 1331 |
# not do the method which isn't listed. The server |
| 1332 |
# won't reject authentication if the supplicant tries |
| 1333 |
# an extra method, but the supplicant is likely to |
| 1334 |
# fail in that case. |
| 1335 |
# |
| 1336 |
# If two methods are listed, then both must be |
| 1337 |
# succeed in order for authentication to succeed. If |
| 1338 |
# one inner method fails, then authentication is |
| 1339 |
# rejected. |
| 1340 |
# |
| 1341 |
# The order of "machine,user" versus "user,machine" |
| 1342 |
# doesn't matter for authentication. Both methods |
| 1343 |
# must still succeed. |
| 1344 |
# |
| 1345 |
# The configuration of "machine,user" versus |
| 1346 |
# "user,machine" changes what method the server |
| 1347 |
# initiates when the supplicant connects. When |
| 1348 |
# authentication starts, the server will initiate the |
| 1349 |
# first method. Once that method succeeds, the |
| 1350 |
# server will initiate the second method. |
| 1351 |
# |
| 1352 |
# Note that the server can suggest "user", and the |
| 1353 |
# supplicant can reply with "machine" authentication |
| 1354 |
# (or vice versa). This is allowed, and doesn't |
| 1355 |
# affect the status of authentication. |
| 1356 |
# |
| 1357 |
# OPTIONAL |
| 1358 |
# |
| 1359 |
# As a special case if two methods are configured, |
| 1360 |
# then one method can be prefixed with a "?" |
| 1361 |
# character. This configuration indicates that the |
| 1362 |
# method is optional. That is, the server will |
| 1363 |
# _suggest_ that method, but will not _require_ it. |
| 1364 |
# |
| 1365 |
# identity_types = "machine,?user" |
| 1366 |
# |
| 1367 |
# If the optional method isn't sent by the |
| 1368 |
# supplicant, that's OK. However, the other method |
| 1369 |
# is still mandatory, and it still must succeed. |
| 1370 |
# |
| 1371 |
# This configuration is most useful when you want to |
| 1372 |
# allow machines to access the network, even if a |
| 1373 |
# user isn't logged into the desktop on that machine. |
| 1374 |
# |
| 1375 |
# This configuration sets &session-state:FreeRADIUS-EAP-TEAP-TLV-Identity-Type with the |
| 1376 |
# relevant values. The TEAP module then picks those values, in order, to authenticate the |
| 1377 |
# chosen identity. You can set &session-state:FreeRADIUS-EAP-TEAP-TLV-Identity-Type |
| 1378 |
# manually, but doing that is substantially more complicated. |
| 1379 |
# |
| 1380 |
# &session-state:TEAP-Type-{Machine,User} will be set |
| 1381 |
# with the EAP type used (set to 'NAK' if skipped and |
| 1382 |
# 'None' for Basic Password Authentication) as each |
| 1383 |
# method completes allowing you to determine with |
| 1384 |
# unlang within post-auth what happened. |
| 1385 |
# |
| 1386 |
# identity_types = "machine,user" |
| 1387 |
|
| 1388 |
# |
| 1389 |
# Set the EAP type for user / machine authentication. |
| 1390 |
# |
| 1391 |
# If set, these values over-ride "default_eap_type" |
| 1392 |
# |
| 1393 |
# These values can be over-ridden at run time by setting |
| 1394 |
# |
| 1395 |
# &session-state:TEAP-Type-User = ... |
| 1396 |
# |
| 1397 |
# and |
| 1398 |
# &session-state:TEAP-Type-Machine = ... |
| 1399 |
# |
| 1400 |
# The values for those attributes are the same as for EAP-Type. |
| 1401 |
# |
| 1402 |
# Note that if you try to use "EAP-Type := TEAP" in the |
| 1403 |
# "inner-tunnel" virtual server, it will not work. |
| 1404 |
# |
| 1405 |
# |
| 1406 |
# PASSWORDS |
| 1407 |
# |
| 1408 |
# Some supplicants support password authentication inside of |
| 1409 |
# TEAP. This can be configured automatically by setting |
| 1410 |
# |
| 1411 |
# identity_type = "user" |
| 1412 |
# |
| 1413 |
# and then not setting "default_eap_type" or |
| 1414 |
# "user_eap_type". The TEAP module will then |
| 1415 |
# automatically initiate password authentication. |
| 1416 |
# |
| 1417 |
# The user credentials are placed into the User-Name |
| 1418 |
# and User-Password attributes inside of the |
| 1419 |
# "inner-tunnel" virtual server. These attributes |
| 1420 |
# are not sent in TEAP, but are created by the module |
| 1421 |
# from the Basic-Password-Auth-Resp TLV which is in TEAP. |
| 1422 |
# |
| 1423 |
# Supported authentication methods inside of TEAP are |
| 1424 |
# EAP-TLS, EAP-MSCHAPv2, and PAP. FreeRADIUS |
| 1425 |
# supports other methods, but the Windows supplicant |
| 1426 |
# does not. |
| 1427 |
# |
| 1428 |
# user_eap_type = mschapv2 |
| 1429 |
# machine_eap_type = tls |
| 1430 |
|
| 1431 |
# |
| 1432 |
# Set the default EAP type. This configuration item |
| 1433 |
# is only used if the "user_eap_type" and |
| 1434 |
# "machine_eap_type" items are not set. |
| 1435 |
# |
| 1436 |
# default_eap_type = mschapv2 |
| 1437 |
|
| 1438 |
# If 'cipher_list' is set here, it will over-ride the |
| 1439 |
# 'cipher_list' configuration from the 'tls-common' |
| 1440 |
# configuration. The EAP-TEAP module has it's own |
| 1441 |
# over-ride for 'cipher_list' because the |
| 1442 |
# specifications mandate a different set of ciphers |
| 1443 |
# than are used by the other EAP methods. |
| 1444 |
# |
| 1445 |
# cipher_list though must include "ADH" for anonymous provisioning. |
| 1446 |
# This is not as straight forward as appending "ADH" alongside |
| 1447 |
# "DEFAULT" as "DEFAULT" contains "!aNULL" so instead it is |
| 1448 |
# recommended "ALL:!EXPORT:!eNULL:!SSLv2" is used |
| 1449 |
# |
| 1450 |
# cipher_list = "ALL:!EXPORT:!eNULL:!SSLv2" |
| 1451 |
|
| 1452 |
# Authority ID of the server |
| 1453 |
# |
| 1454 |
# If you are running a cluster of RADIUS servers, you |
| 1455 |
# should make the value chosen here the same on all |
| 1456 |
# your RADIUS servers. This value should be unique |
| 1457 |
# to your installation. We suggest using a domain |
| 1458 |
# name. |
| 1459 |
# |
| 1460 |
# authority_identity = "1234" |
| 1461 |
|
| 1462 |
# Same as for TTLS, PEAP, etc. |
| 1463 |
# |
| 1464 |
# virtual_server = inner-tunnel |
| 1465 |
#} |
| 1466 |
} |