Administrace komentářů

Zdravím, už se pár dní mořím s nasazením FreeRadiusu – rád bych použil komponentu LDAP (freeradius-ldap) k ověřování uživatelů oproti ActiveDirectory. LDAP umí při přihlašování pomocí atributu msRADIUSFramedIPAddress definovat IP adresu každému uživateli. Problém nastaváva při ověřování uživatele.

Můj LDAP konfigurační soubor:

ldap {
    server = "server.domena.cz"
    identity = "radius@domena.cz"
    password = "SuperTajne:D"
    basedn = "dc=domena,dc=cz"
       filter = "(sAMAccountName=%{Stripped-User-Name:-%{User-Name}})"
       ldap_connections_number = 5
       timeout = 4
       timelimit = 3
       net_timeout = 1
       tls {
               start_tls = yes
       }
       dictionary_mapping = ${confdir}/ldap.attrmap
       edir_account_policy_check = no
       chase-referrals = yes
       rebind = yes
}

Zkouška přihlášení v debagu:

0)   } # filter_username filter_username = notfound
Executing: /usr/bin/ntlm_auth --request-nt-key --username=%{mschap:User-Name:-None} --domain=domena --challenge=%{mschap:Challenge:-00} --nt-response=%{mschap:NT-Response:-00}:
(0)  ntlm_auth : EXPAND --username=%{mschap:User-Name:-None}
(0)  ntlm_auth :    --> --username=test@domena.cz
(0)  ntlm_auth : Creating challenge hash with username: test@domena.cz
(0)  ntlm_auth : EXPAND --challenge=%{mschap:Challenge:-00}
(0)  ntlm_auth :    --> --challenge=f9f8efaa5a9fec8e
(0)  ntlm_auth : EXPAND --nt-response=%{mschap:NT-Response:-00}
(0)  ntlm_auth :    --> --nt-response=f4c3a503b70395fac30d33ada4720d3bf70c034599c416fb
Program returned code (0) and output 'NT_KEY: E41291D32FB91983F6B0F3771BE89F56'
(0)  ntlm_auth : Program executed successfully
(0)   [ntlm_auth] = ok
(0)   [preprocess] = ok
(0)   [chap] = noop
(0)  mschap : Found MS-CHAP attributes.  Setting 'Auth-Type  = mschap'
(0)   [mschap] = ok
(0)   [digest] = noop
(0)  suffix : Checking for suffix after "@"
(0)  suffix : Looking up realm "domena.cz" for User-Name = "test@domena.cz"
(0)  suffix : No such realm "domena.cz"
(0)   [suffix] = noop
(0)  eap : No EAP-Message, not doing EAP
(0)   [eap] = noop
(0)  files : users: Matched entry DEFAULT at line 182
(0)   [files] = ok
rlm_ldap (ldap): Reserved connection (4)
(0) ERROR: ldap : (uid=%u)
(0) ERROR: ldap :       ^ Invalid variable expansion
(0)  ERROR: ldap : Unable to create filter
rlm_ldap (ldap): Released connection (4)
(0)   [ldap] = invalid
(0)  } #  authorize = invalid
(0) Invalid user (ldap: Unable to create filter): [test@domena.cz/ via Auth-Type = MSCHAP>] (from client domena.cz port 640 cli xx.xx.xx.xx)
(0) Using Post-Auth-Type Reject
(0) # Executing group from file /etc/raddb/sites-enabled/default
(0)  Post-Auth-Type REJECT {
(0)  attr_filter.access_reject : EXPAND %{User-Name}
(0)  attr_filter.access_reject :    --> test@domena.cz
(0)  attr_filter.access_reject : Matched entry DEFAULT at line 11
(0)   [attr_filter.access_reject] = updated
(0)   remove_reply_message_if_eap remove_reply_message_if_eap {
(0)     if (&reply:EAP-Message && &reply:Reply-Message) 
(0)     if (&reply:EAP-Message && &reply:Reply-Message)  -> FALSE
(0)    else else {
(0)     [noop] = noop
(0)    } # else else = noop
(0)   } # remove_reply_message_if_eap remove_reply_message_if_eap = noop
(0)  } # Post-Auth-Type REJECT = updated
(0) Delaying response for 1 seconds
Waking up in 0.3 seconds.
Received Access-Request Id 213 from xx.xx.xx.xx:54353 to xx.xx.xx.xx:1812 length 218
(0) Ignoring duplicate packet from client domena.cz port 54353 - ID: 213 due to unfinished request in component core module 
Waking up in 0.6 seconds.
Received Access-Request Id 213 from xx.xx.xx.xx:54353 to xx.xx.xx.xx:1812 length 218
(0) Discarding duplicate request from client domena.cz port 54353 - ID: 213 due to delayed response
Waking up in 0.4 seconds.
(0) Sending delayed response
(0) Sending Access-Reject packet to host xx.xx.xx.xx port 54353, id=213, length=0
Sending Access-Reject Id 213 from xx.xx.xx.xx:1812 to xx.xx.xx.xx:54353
Waking up in 3.9 seconds.
(0) Cleaning up request packet ID 213 with timestamp +4
Ready to process requests

Autorizace ntlm_aut

Pokud použiji pro oveření metodu ntlm_auth tak vše proběhne korektně -> bohužel jsem nepřišel jak definovat pro, každého uživatele IP adresu :(

Dokáže mi někdo poradit ..? Děkuji moc.