| 1 |
# |
| 2 |
# Example configuration for ABFAB listening on TLS. |
| 3 |
# |
| 4 |
# $Id: b8d0626bbe8923a97506b7410e83f88e3af4c42a $ |
| 5 |
# |
| 6 |
listen { |
| 7 |
ipaddr = * |
| 8 |
port = 2083 |
| 9 |
type = auth |
| 10 |
proto = tcp |
| 11 |
|
| 12 |
tls { |
| 13 |
tls_min_version = "1.2" |
| 14 |
private_key_password = whatever |
| 15 |
|
| 16 |
# Moonshot tends to distribute certs separate from keys |
| 17 |
private_key_file = ${certdir}/server.key |
| 18 |
certificate_file = ${certdir}/server.pem |
| 19 |
ca_file = ${cadir}/ca.pem |
| 20 |
dh_file = ${certdir}/dh |
| 21 |
fragment_size = 8192 |
| 22 |
ca_path = ${cadir} |
| 23 |
cipher_list = "DEFAULT" |
| 24 |
cache { |
| 25 |
enable = no |
| 26 |
lifetime = 24 # hours |
| 27 |
name = "abfab-tls" |
| 28 |
# persist_dir = ${logdir}/abfab-tls |
| 29 |
} |
| 30 |
require_client_cert = yes |
| 31 |
verify { |
| 32 |
} |
| 33 |
|
| 34 |
psk_query = "%{psksql:select hex(key) from psk_keys where keyid = '%{TLS-PSK-Identity}'}" |
| 35 |
} |
| 36 |
|
| 37 |
virtual_server = abfab-idp |
| 38 |
clients = radsec-abfab |
| 39 |
} |
| 40 |
|
| 41 |
# There needs to be a separated "listen" section for IPv6. |
| 42 |
# Typically it will be identical to the IPv4 one above, but there might be |
| 43 |
# some differences (e.g. if a different certificate or port is desired) |
| 44 |
listen { |
| 45 |
ipaddr = :: |
| 46 |
port = 2083 |
| 47 |
type = auth |
| 48 |
proto = tcp |
| 49 |
|
| 50 |
tls { |
| 51 |
tls_min_version = "1.2" |
| 52 |
private_key_password = whatever |
| 53 |
|
| 54 |
# Moonshot tends to distribute certs separate from keys |
| 55 |
private_key_file = ${certdir}/server.key |
| 56 |
certificate_file = ${certdir}/server.pem |
| 57 |
ca_file = ${cadir}/ca.pem |
| 58 |
dh_file = ${certdir}/dh |
| 59 |
fragment_size = 8192 |
| 60 |
ca_path = ${cadir} |
| 61 |
cipher_list = "DEFAULT" |
| 62 |
cache { |
| 63 |
enable = no |
| 64 |
lifetime = 24 # hours |
| 65 |
name = "abfab-tls" |
| 66 |
# persist_dir = ${logdir}/abfab-tls |
| 67 |
} |
| 68 |
require_client_cert = yes |
| 69 |
verify { |
| 70 |
} |
| 71 |
|
| 72 |
psk_query = "%{psksql:select hex(key) from psk_keys where keyid = '%{TLS-PSK-Identity}'}" |
| 73 |
} |
| 74 |
|
| 75 |
virtual_server = abfab-idp |
| 76 |
clients = radsec-abfab |
| 77 |
} |
| 78 |
|
| 79 |
clients radsec-abfab { |
| 80 |
# |
| 81 |
# Allow all clients, but require TLS. |
| 82 |
# This client stanza will match other RP proxies from other |
| 83 |
# realms established via the trustrouter. In general |
| 84 |
# additional client stanzas are also required for local services. |
| 85 |
# |
| 86 |
client default { |
| 87 |
ipaddr = 0.0.0.0/0 |
| 88 |
proto = tls |
| 89 |
} |
| 90 |
|
| 91 |
client default_ip6 { |
| 92 |
ipaddr = ::/0 |
| 93 |
proto = tls |
| 94 |
} |
| 95 |
|
| 96 |
# An example local service |
| 97 |
# client service_1 { |
| 98 |
# ipaddr = 192.0.2.20 |
| 99 |
# # You should either set gss_acceptor_host_name below |
| 100 |
# # or set up policy to confirm that a client claims |
| 101 |
# # the right acceptor hostname when using ABFAB. If |
| 102 |
# # set, the RADIUS server will confirm that all |
| 103 |
# # requests have this value for the acceptor host name |
| 104 |
# gss_acceptor_host_name = "server.example.com" |
| 105 |
# # If set, this acceptor realm name will be included. |
| 106 |
# # Foreign realms will typically reject a request if this is not |
| 107 |
# # properly set. |
| 108 |
# gss_acceptor_realm_name = "example.com" |
| 109 |
# # Additionally, trust_router_coi can be set; if set |
| 110 |
# # it will override the default_community in the realm |
| 111 |
# # module |
| 112 |
# trust_router_coi = "community1.example.net" |
| 113 |
# # In production depployments it is important to set |
| 114 |
# # up certificate verification so that even if |
| 115 |
# # clients spoof IP addresses, one client cannot |
| 116 |
# # impersonate another. |
| 117 |
# } |
| 118 |
} |