Re: FR2.1.3+LDAP+802.1x+PEAP
Hi Alan, thank you for your answer, that page/table was awesome regarding your tips: a) i dont wanna do, maybe if i have no other choice, ill have 2 password attributes SSHA+NTLM, but its a clear no to clear-text, and a maybe to NT hash b) need it, so not gonna happen so, as i need to proceed further with my investigation, what are my options really? :D i was thinking at the following: to do the normal user authentication in LDAP, based on the provided realm, and if no realm present authenticate the users in users file. Users which use 802.1x will be saved in clear-text in users file and users used for authentication for other stuff, will be checked in LDAP (@mydomain.com) or can i switch this around? a user: myuser@dot1x.com will be based on the real authenticated in users file for 802.1x and a user with no realm will be authenticated in LDAP? please tell me your opinion on this, is it possible? Thanks & Best Regards, Caius Pargar
i was thinking at the following: to do the normal user authentication in LDAP, based on the provided realm, and if no realm present authenticate the users in users file. Users which use 802.1x will be saved in clear-text in users file and users used for authentication for other stuff, will be checked in LDAP (@mydomain.com)
or can i switch this around? a user: myuser@dot1x.com will be based on the real authenticated in users file for 802.1x and a user with no realm will be authenticated in LDAP?
please tell me your opinion on this, is it possible?
Use suffix and configure dot1x.com as local realm in proxy.conf: realm dot1x.com { } ... and you don't need multiple entries for the same user. Both users file and ldap module will use Stripped-User-Name for authentication by defauly. Ivan Kalik Kalik Informatika ISP
Hi Ivan, my problem was that in LDAP i have the passwords save as SSHA, so i cant do 802.1x with EAP/PEAP/mschap as i dont wanna change my LDAP configuration to store the passwords in clear-text, or to use samba.scheme and to use NT hash. The only option remaining from my view point was to try and distinguish between normal authentication and 802.1x authentication thats why i came up with this realm stuff, to be able to authenticate 802.1x users in the users file (where i have user/passwords in clear-text) and normal users in LDAP (SSHA) thats why i was asking if, its possible, and if it functional, or maybe there is another solution then the one provided by Alan (to not use 802.1x) :D thank you again for you feedback Best Regards, Caius Pargar --- On Wed, 11/11/09, tnt@kalik.net <tnt@kalik.net> wrote:
From: tnt@kalik.net <tnt@kalik.net> Subject: Re: FR2.1.3+LDAP+802.1x+PEAP To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Date: Wednesday, November 11, 2009, 1:06 AM
i was thinking at the following: to do the normal user authentication in LDAP, based on the provided realm, and if no realm present authenticate the users in users file. Users which use 802.1x will be saved in clear-text in users file and users used for authentication for other stuff, will be checked in LDAP (@mydomain.com)
or can i switch this around? a user: myuser@dot1x.com will be based on the real authenticated in users file for 802.1x and a user with no realm will be authenticated in LDAP?
please tell me your opinion on this, is it possible?
Use suffix and configure dot1x.com as local realm in proxy.conf:
realm dot1x.com { }
... and you don't need multiple entries for the same user. Both users file and ldap module will use Stripped-User-Name for authentication by defauly.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
my problem was that in LDAP i have the passwords save as SSHA, so i cant do 802.1x with EAP/PEAP/mschap
as i dont wanna change my LDAP configuration to store the passwords in clear-text, or to use samba.scheme and to use NT hash. The only option remaining from my view point was to try and distinguish between normal authentication and 802.1x authentication
thats why i came up with this realm stuff, to be able to authenticate 802.1x users in the users file (where i have user/passwords in clear-text) and normal users in LDAP (SSHA)
Ugh, how does that make sense? Why don't you want nt or clear passwords in ldap? Security? But it's so much easier to read a plain text (users) file than break into ldap.
thats why i was asking if, its possible, and if it functional, or maybe there is another solution then the one provided by Alan (to not use 802.1x) :D
There is only one solution if you want to use 802.1x: store passwords that peap can use. Ivan Kalik Kalik Informatika ISP
Hi Ivan, i know about the restrictions, but do you know how weak that NT hash is? from what i know its MD4 hashing, where is that use nowadays? not even MD5 is used anymore ... the MD4 algorithm was one of the earliest MD algorithms ... made in '90, and MD5 came as a improvement and is to this day the most popular. MD5 should be the most secure of the MD bunch but even so it has been shown to be abnormally susceptible to collisions, and its use is now actively discouraged so i cant afford to make all my user password hash weak... also i need to respect some security guidelines in my system. i could go to use only clear-text for 802.1x users, have a exception for this kid of users. thats why im thinking to try some filtering... based on the NAS-ID or NAS-IP i might authenticate the users in users file or LDAP, right? :D thank you again for your thoughts on this Best Regards, Caius Pargar --- On Wed, 11/11/09, tnt@kalik.net <tnt@kalik.net> wrote:
From: tnt@kalik.net <tnt@kalik.net> Subject: Re: FR2.1.3+LDAP+802.1x+PEAP To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Date: Wednesday, November 11, 2009, 8:53 PM
my problem was that in LDAP i have the passwords save as SSHA, so i cant do 802.1x with EAP/PEAP/mschap
as i dont wanna change my LDAP configuration to store the passwords in clear-text, or to use samba.scheme and to use NT hash. The only option remaining from my view point was to try and distinguish between normal authentication and 802.1x authentication
thats why i came up with this realm stuff, to be able to authenticate 802.1x users in the users file (where i have user/passwords in clear-text) and normal users in LDAP (SSHA)
Ugh, how does that make sense? Why don't you want nt or clear passwords in ldap? Security? But it's so much easier to read a plain text (users) file than break into ldap.
thats why i was asking if, its possible, and if it functional, or maybe there is another solution then the one provided by Alan (to not use 802.1x) :D
There is only one solution if you want to use 802.1x: store passwords that peap can use.
Ivan Kalik Kalik Informatika ISP
Caius wrote:
i know about the restrictions, but do you know how weak that NT hash is?
Everyone knows.
so i cant afford to make all my user password hash weak...
Perhaps you didn't read the web page on deployingradius.com. If you want to do PEAP, the ONLY CHOICE you have is whether to store clear-text passwords, or NT hashed passwords. Saying you "can't afford" to use NT hash is like saying "I want to drive a car, but I can't afford the time to learn how".
also i need to respect some security guidelines in my system.
Too bad. If your security system forbids clear-text passwords && NT hashed passwords, then it forbids EAP. That's what the web page says. If it's not clear, go read it again.
i could go to use only clear-text for 802.1x users, have a exception for this kid of users.
thats why im thinking to try some filtering... based on the NAS-ID or NAS-IP i might authenticate the users in users file or LDAP, right? :D
Put the 802.1X capable users into an LDAP group. Forbid anyone else from doing 802.1X. And store the passwords clear-text or NT hashed. Use LDAP ACLs to limit access to them. Alan DeKok.
Hi Alan, your right in what you say, My conclusion is: i could go for EAP-TTLS + xsupplicant (there is also a windows version), then i dont need to weaken my server security, but i force the client to install a 3th party tool or as discuses with Ivan, i could make some rules, based on the NAS-ID or NAS-IP, where to check for the 802.1x users (in users file), right? ill do tomorrow some tests with this solutions and see if i have some problems thanks again for your patience and clear answers, Best Regards, Caius Pargar --- On Thu, 11/12/09, Alan DeKok <aland@deployingradius.com> wrote:
From: Alan DeKok <aland@deployingradius.com> Subject: Re: FR2.1.3+LDAP+802.1x+PEAP To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Date: Thursday, November 12, 2009, 10:18 AM Caius wrote:
i know about the restrictions, but do you know how weak that NT hash is?
Everyone knows.
so i cant afford to make all my user password hash weak...
Perhaps you didn't read the web page on deployingradius.com.
If you want to do PEAP, the ONLY CHOICE you have is whether to store clear-text passwords, or NT hashed passwords.
Saying you "can't afford" to use NT hash is like saying "I want to drive a car, but I can't afford the time to learn how".
also i need to respect some security guidelines in my system.
Too bad. If your security system forbids clear-text passwords && NT hashed passwords, then it forbids EAP.
That's what the web page says. If it's not clear, go read it again.
i could go to use only clear-text for 802.1x users, have a exception for this kid of users.
thats why im thinking to try some filtering... based on the NAS-ID or NAS-IP i might authenticate the users in users file or LDAP, right? :D
Put the 802.1X capable users into an LDAP group. Forbid anyone else from doing 802.1X.
And store the passwords clear-text or NT hashed. Use LDAP ACLs to limit access to them.
Alan DeKok.
My conclusion is: i could go for EAP-TTLS + xsupplicant (there is also a windows version), then i dont need to weaken my server security, but i force the client to install a 3th party tool
People also use SecureW2. Compare and see which one is better.
or as discuses with Ivan, i could make some rules, based on the NAS-ID or NAS-IP, where to check for the 802.1x users (in users file), right?
I never said that was a good idea ;-) On the contrary, I pointed out serious security flaws in that approach. If you are adamant that you want to keep encrypted password incompatible with peap, TTLS/PAP is the way to go. Ivan Kalik Kalik Informatika ISP
Hi all, i followed the how-to steps from http://deployingradius.com/documents/configuration/setup.html configured PAP, and EAP, made the certificates using the defaults in ./certs/bootstrap Also: in the authenticate {} section from ./sites-available/default Auth-Type LDAP { ldap } other changes shouldnt be, i tried to make as little changes as necessary, hope i didnt blew it..... i have a SUN station with Solaris 10, use Sun Directory Server for LDAP (passwords with SSHA) + freeRADIUS_v2.1.7 local test was successful (the last lines/attempt ), but when using the Xsupplicant windows client (the first attempt) connected to the Alcatel-Lucent OmniSwitch 6850 (as NAS client), it didnt as it returned failed to authenticate user. Im thinking that maybe, i need to tweak something in the TTLS attributes, or make some changes in the inner-tunnel file i have in TTLS section of eap.conf: copy_request_to_tunnel = yes use_tunneled_reply = yes anyway, here is the log from radiusd -fX $/usr/local/sbin/radiusd -fX FreeRADIUS Version 2.1.7, for host sparc-sun-solaris2.10, built on Nov 12 2009 at 14:49:13 Copyright (C) 1999-2009 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License v2. Starting - reading configuration files ... including configuration file /usr/local/etc/raddb/radiusd.conf including configuration file /usr/local/etc/raddb/proxy.conf including configuration file /usr/local/etc/raddb/clients.conf including files in directory /usr/local/etc/raddb/modules/ including configuration file /usr/local/etc/raddb/modules/acct_unique including configuration file /usr/local/etc/raddb/modules/always including configuration file /usr/local/etc/raddb/modules/attr_filter including configuration file /usr/local/etc/raddb/modules/attr_rewrite including configuration file /usr/local/etc/raddb/modules/chap including configuration file /usr/local/etc/raddb/modules/checkval including configuration file /usr/local/etc/raddb/modules/counter including configuration file /usr/local/etc/raddb/modules/cui including configuration file /usr/local/etc/raddb/modules/detail including configuration file /usr/local/etc/raddb/modules/detail.example.com including configuration file /usr/local/etc/raddb/modules/detail.log including configuration file /usr/local/etc/raddb/modules/digest including configuration file /usr/local/etc/raddb/modules/echo including configuration file /usr/local/etc/raddb/modules/etc_group including configuration file /usr/local/etc/raddb/modules/exec including configuration file /usr/local/etc/raddb/modules/expiration including configuration file /usr/local/etc/raddb/modules/expr including configuration file /usr/local/etc/raddb/modules/files including configuration file /usr/local/etc/raddb/modules/inner-eap including configuration file /usr/local/etc/raddb/modules/ippool including configuration file /usr/local/etc/raddb/modules/krb5 including configuration file /usr/local/etc/raddb/modules/ldap including configuration file /usr/local/etc/raddb/modules/linelog including configuration file /usr/local/etc/raddb/modules/logintime including configuration file /usr/local/etc/raddb/modules/mac2ip including configuration file /usr/local/etc/raddb/modules/mschap including configuration file /usr/local/etc/raddb/modules/mac2vlan including configuration file /usr/local/etc/raddb/modules/otp including configuration file /usr/local/etc/raddb/modules/pam including configuration file /usr/local/etc/raddb/modules/pap including configuration file /usr/local/etc/raddb/modules/passwd including configuration file /usr/local/etc/raddb/modules/perl including configuration file /usr/local/etc/raddb/modules/policy including configuration file /usr/local/etc/raddb/modules/preprocess including configuration file /usr/local/etc/raddb/modules/radutmp including configuration file /usr/local/etc/raddb/modules/realm including configuration file /usr/local/etc/raddb/modules/smbpasswd including configuration file /usr/local/etc/raddb/modules/smsotp including configuration file /usr/local/etc/raddb/modules/sql_log including configuration file /usr/local/etc/raddb/modules/sqlcounter_expire_on_login including configuration file /usr/local/etc/raddb/modules/sradutmp including configuration file /usr/local/etc/raddb/modules/unix including configuration file /usr/local/etc/raddb/modules/wimax including configuration file /usr/local/etc/raddb/eap.conf including configuration file /usr/local/etc/raddb/policy.conf including files in directory /usr/local/etc/raddb/sites-enabled/ including configuration file /usr/local/etc/raddb/sites-enabled/default including configuration file /usr/local/etc/raddb/sites-enabled/inner-tunnel including configuration file /usr/local/etc/raddb/sites-enabled/control-socket including dictionary file /usr/local/etc/raddb/dictionary main { prefix = "/usr/local" localstatedir = "/usr/local/var" logdir = "/usr/local/var/log/radius" libdir = "/usr/local/lib" radacctdir = "/usr/local/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 allow_core_dumps = no pidfile = "/usr/local/var/run/radiusd/radiusd.pid" checkrad = "/usr/local/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = no auth_badpass = no auth_goodpass = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 require_message_authenticator = no zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } client switvh { ipaddr = 192.168.101.122 require_message_authenticator = no secret = "challenge" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating expr Module: Linked to module rlm_expiration Module: Instantiating expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating pap pap { encryption_scheme = "auto" auto_header = yes } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "ttls" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no max_sessions = 2048 } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 pem_file_type = yes private_key_file = "/usr/local/etc/raddb/certs/server.pem" certificate_file = "/usr/local/etc/raddb/certs/server.pem" CA_file = "/usr/local/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/usr/local/etc/raddb/certs/dh" random_file = "/usr/local/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/usr/local/etc/raddb/certs/bootstrap" cache { enable = no lifetime = 24 max_entries = 255 } } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "md5" copy_request_to_tunnel = yes use_tunneled_reply = yes virtual_server = "inner-tunnel" include_length = yes } Module: Linked to sub-module rlm_eap_peap Module: Instantiating eap-peap peap { default_eap_type = "mschapv2" copy_request_to_tunnel = no use_tunneled_reply = no proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/usr/local/var/log/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Linked to module rlm_attr_filter Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/usr/local/etc/raddb/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/usr/local/var/log/radius/radwtmp" } Module: Linked to module rlm_ldap Module: Instantiating ldap ldap { server = "host20" port = 389 password = "ldaptest" identity = "cn=directory manager" net_timeout = 1 timeout = 4 timelimit = 3 tls_mode = no start_tls = no tls_require_cert = "allow" tls { start_tls = no require_cert = "allow" } basedn = "dc=blackbox,dc=com" filter = "(uid=%{%{Stripped-User-Name}:-%{User-Name}})" base_filter = "(objectclass=radiusprofile)" auto_header = no access_attr = "radiusFilterId" access_attr_used_for_allow = yes groupname_attribute = "cn" groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" dictionary_mapping = "/usr/local/etc/raddb/ldap.attrmap" ldap_debug = 0 ldap_connections_number = 5 compare_check_items = no do_xlat = yes set_auth_type = yes } rlm_ldap: Registering ldap_groupcmp for Ldap-Group rlm_ldap: Registering ldap_xlat with xlat_name ldap rlm_ldap: reading ldap<->radius mappings from file /usr/local/etc/raddb/ldap.attrmap rlm_ldap: LDAP radiusCheckItem mapped to RADIUS $GENERIC$ rlm_ldap: LDAP radiusReplyItem mapped to RADIUS $GENERIC$ rlm_ldap: LDAP radiusAuthType mapped to RADIUS Auth-Type rlm_ldap: LDAP radiusSimultaneousUse mapped to RADIUS Simultaneous-Use rlm_ldap: LDAP radiusCalledStationId mapped to RADIUS Called-Station-Id rlm_ldap: LDAP radiusCallingStationId mapped to RADIUS Calling-Station-Id rlm_ldap: LDAP lmPassword mapped to RADIUS LM-Password rlm_ldap: LDAP ntPassword mapped to RADIUS NT-Password rlm_ldap: LDAP sambaLmPassword mapped to RADIUS LM-Password rlm_ldap: LDAP sambaNtPassword mapped to RADIUS NT-Password rlm_ldap: LDAP dBCSPwd mapped to RADIUS LM-Password rlm_ldap: LDAP acctFlags mapped to RADIUS SMB-Account-CTRL-TEXT rlm_ldap: LDAP radiusExpiration mapped to RADIUS Expiration rlm_ldap: LDAP radiusNASIpAddress mapped to RADIUS NAS-IP-Address rlm_ldap: LDAP radiusServiceType mapped to RADIUS Service-Type rlm_ldap: LDAP radiusFramedProtocol mapped to RADIUS Framed-Protocol rlm_ldap: LDAP radiusFramedIPAddress mapped to RADIUS Framed-IP-Address rlm_ldap: LDAP radiusFramedIPNetmask mapped to RADIUS Framed-IP-Netmask rlm_ldap: LDAP radiusFramedRoute mapped to RADIUS Framed-Route rlm_ldap: LDAP radiusFramedRouting mapped to RADIUS Framed-Routing rlm_ldap: LDAP radiusFilterId mapped to RADIUS Filter-Id rlm_ldap: LDAP radiusFramedMTU mapped to RADIUS Framed-MTU rlm_ldap: LDAP radiusFramedCompression mapped to RADIUS Framed-Compression rlm_ldap: LDAP radiusLoginIPHost mapped to RADIUS Login-IP-Host rlm_ldap: LDAP radiusLoginService mapped to RADIUS Login-Service rlm_ldap: LDAP radiusLoginTCPPort mapped to RADIUS Login-TCP-Port rlm_ldap: LDAP radiusCallbackNumber mapped to RADIUS Callback-Number rlm_ldap: LDAP radiusCallbackId mapped to RADIUS Callback-Id rlm_ldap: LDAP radiusFramedIPXNetwork mapped to RADIUS Framed-IPX-Network rlm_ldap: LDAP radiusClass mapped to RADIUS Class rlm_ldap: LDAP radiusSessionTimeout mapped to RADIUS Session-Timeout rlm_ldap: LDAP radiusIdleTimeout mapped to RADIUS Idle-Timeout rlm_ldap: LDAP radiusTerminationAction mapped to RADIUS Termination-Action rlm_ldap: LDAP radiusLoginLATService mapped to RADIUS Login-LAT-Service rlm_ldap: LDAP radiusLoginLATNode mapped to RADIUS Login-LAT-Node rlm_ldap: LDAP radiusLoginLATGroup mapped to RADIUS Login-LAT-Group rlm_ldap: LDAP radiusFramedAppleTalkLink mapped to RADIUS Framed-AppleTalk-Link rlm_ldap: LDAP radiusFramedAppleTalkNetwork mapped to RADIUS Framed-AppleTalk-Network rlm_ldap: LDAP radiusFramedAppleTalkZone mapped to RADIUS Framed-AppleTalk-Zone rlm_ldap: LDAP radiusPortLimit mapped to RADIUS Port-Limit rlm_ldap: LDAP radiusLoginLATPort mapped to RADIUS Login-LAT-Port rlm_ldap: LDAP radiusReplyMessage mapped to RADIUS Reply-Message rlm_ldap: LDAP radiusTunnelType mapped to RADIUS Tunnel-Type rlm_ldap: LDAP radiusTunnelMediumType mapped to RADIUS Tunnel-Medium-Type rlm_ldap: LDAP radiusTunnelPrivateGroupId mapped to RADIUS Tunnel-Private-Group-Id conns: 15e330 Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/usr/local/etc/raddb/huntgroups" hints = "/usr/local/etc/raddb/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating detail detail { detailfile = "/usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/usr/local/etc/raddb/attrs.accounting_response" key = "%{User-Name}" } Module: Checking session {...} for more modules to load Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load } # modules } # server radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } listen { type = "control" listen { socket = "/usr/local/var/run/radiusd/radiusd.sock" } } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 192.168.101.122 port 1038, id=207, length=95 User-Name = "testuser" NAS-IP-Address = 192.168.101.122 NAS-Port = 1029 NAS-Port-Type = Async Calling-Station-Id = "002186961979" EAP-Message = 0x0200000d017465737475736572 Message-Authenticator = 0x17dcf8b04495aa1127dcc2f8d5c72633 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 0 length 13 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns updated ++[files] returns noop [ldap] performing user authorization for testuser [ldap] expand: %{Stripped-User-Name} -> [ldap] expand: %{User-Name} -> testuser [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=testuser) [ldap] expand: dc=blackbox,dc=com -> dc=blackbox,dc=com rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: attempting LDAP reconnection rlm_ldap: (re)connect to host20:389, authentication 0 rlm_ldap: bind as cn=directory manager/ldaptest to host20:389 rlm_ldap: waiting for bind result ... rlm_ldap: Bind was successful rlm_ldap: performing search in dc=blackbox,dc=com, with filter (uid=testuser) [ldap] checking if remote access for testuser is allowed by radiusFilterId [ldap] looking for check items in directory... [ldap] looking for reply items in directory... rlm_ldap: radiusFilterId -> Filter-Id = "TunnelMgtGroup" WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ldap] user testuser authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 207 to 192.168.101.122 port 1038 Filter-Id = "TunnelMgtGroup" EAP-Message = 0x010100061520 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x2e443a5b2e452f244b88bd87cfbeed10 Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.101.122 port 1038, id=208, length=194 User-Name = "testuser" NAS-IP-Address = 192.168.101.122 State = 0x2e443a5b2e452f244b88bd87cfbeed10 NAS-Port = 1029 NAS-Port-Type = 1952805748 Calling-Station-Id = "002186961979" EAP-Message = 0x0201005e150016030100530100004f03014b010a55a8baef6f4d89e1308789a1c87c08d79a72d9ceea5149be9db2a9119b00002800390038003500160013000a00330032002f000700050004001500120009001400110008000600030100 Message-Authenticator = 0x95c0d5bf3dd1fed4dfc0a4a6e6b75484 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 1 length 94 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] eaptls_verify returned 7 [ttls] Done initial handshake [ttls] (other): before/accept initialization [ttls] TLS_accept: before/accept initialization [ttls] <<< TLS 1.0 Handshake [length 0053], ClientHello [ttls] TLS_accept: SSLv3 read client hello A [ttls] >>> TLS 1.0 Handshake [length 002a], ServerHello [ttls] TLS_accept: SSLv3 write server hello A [ttls] >>> TLS 1.0 Handshake [length 085e], Certificate [ttls] TLS_accept: SSLv3 write certificate A [ttls] >>> TLS 1.0 Handshake [length 020d], ServerKeyExchange [ttls] TLS_accept: SSLv3 write key exchange A [ttls] >>> TLS 1.0 Handshake [length 0004], ServerHelloDone [ttls] TLS_accept: SSLv3 write server done A [ttls] TLS_accept: SSLv3 flush data [ttls] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [ttls] eaptls_process returned 13 ++[eap] returns handled Sending Access-Challenge of id 208 to 192.168.101.122 port 1038 EAP-Message = 0x0102040015c000000aad160301002a0200002603014b010dc148ef5e030df0092c526c46a63a403e210c91c3ac377cb4e4ffead0a200003900160301085e0b00085a0008570003a6308203a23082028aa003020102020101300d06092a864886f70d0101040500308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479 EAP-Message = 0x301e170d3039313131333136333331395a170d3130313131333136333331395a307c310b3009060355040613024652310f300d0603550408130652616469757331153013060355040a130c4578616d706c6520496e632e312330210603550403131a4578616d706c65205365727665722043657274696669636174653120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d30820122300d06092a864886f70d01010105000382010f003082010a0282010100c8e36e913fa5a280a08e636640a42cd1e3f9609a202b1efd415d0a062e0cbf496fb5f6247a1bb209e038f7b941cdedb39cedc7d348483066476d98897488 EAP-Message = 0x7b19c8083ce6ec6baabd8d193db7f40e0476c6825672174655b10a8382b5ba098f2a06df627562f27bcfafc1064b5962da61857aae5ee4dddeba556d81d24d5a6a302c44068dcd60f64e1485f1bb5a809016e453f0b72c2ca03b37f01e0cf058cac17fe04f63a9017c29a76e61a048f727c922861bac58a88e0df231705f443d1e559bcd2b6c92d0ff30a4236425fc18b008a266814c080c9aa78a8bf839a29b4056ca67dd8c395b6830ce42d6a69463091fe78e2248c5c9f33ae2890b07e44719f70203010001a317301530130603551d25040c300a06082b06010505070301300d06092a864886f70d010104050003820101009880d61470c6816e98 EAP-Message = 0xf37ddab15e84accf4676b81560e33aa995a0a6f61cb3e152053d71cfc0c9fbcf56915139e3fda56f17685e8b9c2c1e2078bc896ca03c6b1df06b1fa00122ed57b2164cd678b5981e1ea5a3e295e3bc924ab91dd8d581bbb73a4a0dad0e278fe23314c448617998596c26d5c5350128d1f334148eb611c3312ce00223fe34f2ae56ef88d5273baefe6d2599a971b6202bb6aab3759b9e380a6a36bf80d5ff4de7737a3b28ef84a085d7a77136f0a927a26d9a6e2b1d94ff8b81d44b959f17b7e2cf8a9b6ffb429a01a34f2ce962ee870d8c1b30a37951ca151599b5a1c3579e2fca65e7bea0ebc875c500b8c30190fdf8e194b5215abfb60004ab308204 EAP-Message = 0xa73082038fa0030201020209 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x2e443a5b2f462f244b88bd87cfbeed10 Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.101.122 port 1038, id=209, length=106 User-Name = "testuser" NAS-IP-Address = 192.168.101.122 State = 0x2e443a5b2f462f244b88bd87cfbeed10 NAS-Port = 1029 NAS-Port-Type = 1952805748 Calling-Station-Id = "002186961979" EAP-Message = 0x020200061500 Message-Authenticator = 0xacfc7ec8e4c6ac2281265f4c44c81799 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 2 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] Received TLS ACK [ttls] ACK handshake fragment handler [ttls] eaptls_verify returned 1 [ttls] eaptls_process returned 13 ++[eap] returns handled Sending Access-Challenge of id 209 to 192.168.101.122 port 1038 EAP-Message = 0x0103040015c000000aad00afef2c6f3f033745300d06092a864886f70d0101050500308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479301e170d3039313131333136333331395a170d3130313131333136333331395a308193310b3009060355040613024652310f300d0603550408130652616469757331123010 EAP-Message = 0x06035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f7269747930820122300d06092a864886f70d01010105000382010f003082010a0282010100d84504c4853e5ef17da0c447627b2ab6952957a179fd6d7e0fd5c4b5ab4cd6c5fd158d9188361ed46b282e33bd24f9b1217d1341646a2e584e3bd07aa3980b83379a85a0e8299ef20fc720afcffe2aaf906f1b9a366bb0fc3bb8840e332f7dab519b26ff6541353b411649 EAP-Message = 0x64faa3cf6056ba61f36a8d0dc789b22b49b55a031a9d5b4dbc76de968fd39fb365357fb2684f2a54ef1b55e6bb869bc826ef777bc9fcde81c1e9bb33a504e66ebd7bf5abb6b1179d458c8822971f2b33a2b0b04c354179d1416fd66becfb0fa3298728ca9bebf08b2bbebbbdc68866cb435fd753964337acc0ecbcc76cf1cffba965bc6bc31ab80095d23bb7cc61ec5d9f7cce865d0203010001a381fb3081f8301d0603551d0e0416041484069da5717cd36fb1d5f0bc1569adc52fc6b36d3081c80603551d230481c03081bd801484069da5717cd36fb1d5f0bc1569adc52fc6b36da18199a48196308193310b3009060355040613024652310f300d EAP-Message = 0x060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479820900afef2c6f3f033745300c0603551d13040530030101ff300d06092a864886f70d010105050003820101007334ac30325e8ac8d218b8a50603c03e6c42d238daec4b2b525e935fddef3e716336dde4e930c3e8695b36faf69cafa156b1d4e35707ce8582b9e3723d030ed38a6338f5834bd922017dd9c88d58 EAP-Message = 0xee19ebfdebef449a1703937b Message-Authenticator = 0x00000000000000000000000000000000 State = 0x2e443a5b2c472f244b88bd87cfbeed10 Finished request 2. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.101.122 port 1038, id=210, length=106 User-Name = "testuser" NAS-IP-Address = 192.168.101.122 State = 0x2e443a5b2c472f244b88bd87cfbeed10 NAS-Port = 1029 NAS-Port-Type = 1952805748 Calling-Station-Id = "002186961979" EAP-Message = 0x020300061500 Message-Authenticator = 0x27092cbd4483b560ad89cc86d1f9a680 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 3 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] Received TLS ACK [ttls] ACK handshake fragment handler [ttls] eaptls_verify returned 1 [ttls] eaptls_process returned 13 ++[eap] returns handled Sending Access-Challenge of id 210 to 192.168.101.122 port 1038 EAP-Message = 0x010402cb158000000aadebc2b9b8992699ba98b576d89c8086c56ebae18246adf3df7df97bcd4ed37852fe02f96055849714c028618aa39c1113a02dd1bb995521ef31c1f6b9cde1dc46ee8190fbf196c310157f10308aad0e1c745646a14cc725f9859ab163461b423cc12a75402b9620eb80d95946b0369f3c9f093c973fd035553f0db838ef575f117c48a9dc70cd14edfe421027327206ae533b5b8fefcc508cb8cf6f2f2282f9d809ab4f8e187e160301020d0c0002090080918c432a605d54315911fe7789e7ce26d988f3587c07d0d42e9819a70d7c2690307d734bd865bbf10d2d5ee27b0722618121c6c86e549ab5fe76779c696223fc1b9b EAP-Message = 0x5ccee23b0e15fb606440f16277c1e912a5bc31f8889a7b136964ebe9b0acb6dd5e2b0bcef2bdf0ca6d6e4787892991d51b0236764d86734875dd089f515300010200800b707d3475e8c84ee3952a59dc8948016bad084ed8503e67cffcbab98b2e35baffffbafa8e636e2c596137bae0e589c3a148072080638ceba584817b06c32833582d326c6450f54820eb9703bb2c3e266f2a3b7f6d319ba81d1a4b2dd0df4c8382694f4820ecfe35c138c021092c3e100251d827ad222f0a1eaa6e961b2af5e70100c83742913c48f2f5673ad7a00ecdf53d1c235a8d2c8c8e3e35c0d945df896c2c5db03b8315ac33352004b50d5b264559568506798bdb81a3 EAP-Message = 0x7e1227951007cdac5d199b0746aea78fb2fba5b01307c8cd346b595934e2a4779ce9a03efe7a1870bc634def1671590ce3e452b56a9d08a461b218203b729a90a5472d0e6db845f7fbbfe2d864a6237ada12322497c230b3d4906412e2f355eed6093074f88f93aadb40564676065fee4b948a185989bfa8c9b70ca1135f9d57ecd7eeb3dc496b0af4b378835fa733207f435999303605cba62a98306da28990132d355a72df0ed6d8e26cd5ec26ec9c17a5b90ca7ccc5ee3aff2770325adc614934fdd7fc4fa34b16030100040e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x2e443a5b2d402f244b88bd87cfbeed10 Finished request 3. Going to the next request Waking up in 4.8 seconds. rad_recv: Access-Request packet from host 192.168.101.122 port 1038, id=211, length=304 User-Name = "testuser" NAS-IP-Address = 192.168.101.122 State = 0x2e443a5b2d402f244b88bd87cfbeed10 NAS-Port = 1029 NAS-Port-Type = 1952805748 Calling-Station-Id = "002186961979" EAP-Message = 0x020400cc1500160301008610000082008023b18c87ede8bc2bb4a8a672c5d0eea801ed3c0387cb267c2aad9818ac37e2d579e28ab892c81f6bda34ccc6c889344255c65d7a03838484d5caac1ef0307a5f1ed94b4866353f1b6702d8f0f599df6dcd4adba524d133d53ae2b67ff9b651ae41491fd251bbea4337f4dadd85aca8f6669f3b73d98b951ddc7176b98867d5c31403010001011603010030944c712de57a29f7e302e0810bbf504cae5fa9f58982c2999808c548fbd357d4554935dd15cf4584f7c5eba4f2a215a8 Message-Authenticator = 0xfedff7b67ed7cf2666247d94ba826121 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 4 length 204 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] eaptls_verify returned 7 [ttls] Done initial handshake [ttls] <<< TLS 1.0 Handshake [length 0086], ClientKeyExchange [ttls] TLS_accept: SSLv3 read client key exchange A [ttls] <<< TLS 1.0 ChangeCipherSpec [length 0001] [ttls] <<< TLS 1.0 Handshake [length 0010], Finished [ttls] TLS_accept: SSLv3 read finished A [ttls] >>> TLS 1.0 ChangeCipherSpec [length 0001] [ttls] TLS_accept: SSLv3 write change cipher spec A [ttls] >>> TLS 1.0 Handshake [length 0010], Finished [ttls] TLS_accept: SSLv3 write finished A [ttls] TLS_accept: SSLv3 flush data [ttls] (other): SSL negotiation finished successfully SSL Connection Established [ttls] eaptls_process returned 13 ++[eap] returns handled Sending Access-Challenge of id 211 to 192.168.101.122 port 1038 EAP-Message = 0x0105004515800000003b1403010001011603010030f13b13522c3fc7c89efb75bf7b81451eea7bfc61fc2c6ae4e7e0d1294feb0d4236cc981baa1c7929e1668ff46cb11eaf Message-Authenticator = 0x00000000000000000000000000000000 State = 0x2e443a5b2a412f244b88bd87cfbeed10 Finished request 4. Going to the next request Waking up in 4.8 seconds. rad_recv: Access-Request packet from host 192.168.101.122 port 1038, id=212, length=175 User-Name = "testuser" NAS-IP-Address = 192.168.101.122 State = 0x2e443a5b2a412f244b88bd87cfbeed10 NAS-Port = 1029 NAS-Port-Type = 1952805748 Calling-Station-Id = "002186961979" EAP-Message = 0x0205004b15001703010040e65aa70b9d3bf376417c51aeabc0a4531b4a7b48a6cdbcc3c33ebf4ab249ac0f05e36c2d9d635cf333dbcf6aa59a75560a8fa6c5b35e434a2dd7917a65eabad6 Message-Authenticator = 0x2b37b4e7b1362c43eacd53cd45abb630 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 5 length 75 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] eaptls_verify returned 7 [ttls] Done initial handshake [ttls] eaptls_process returned 7 [ttls] Session established. Proceeding to decode tunneled attributes. [ttls] Got tunneled request User-Name = "testuser" User-Password = "Secret149" FreeRADIUS-Proxied-To = 127.0.0.1 [ttls] Sending tunneled request User-Name = "testuser" User-Password = "Secret149" FreeRADIUS-Proxied-To = 127.0.0.1 NAS-IP-Address = 192.168.101.122 NAS-Port = 1029 NAS-Port-Type = 1952805748 Calling-Station-Id = "002186961979" server inner-tunnel { +- entering group authorize {...} [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop ++[control] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel [ttls] Got tunneled reply code 3 [ttls] Got tunneled Access-Reject [eap] Handler failed in EAP/ttls [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> testuser attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 5 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 5 Sending Access-Reject of id 212 to 192.168.101.122 port 1038 EAP-Message = 0x04050004 Message-Authenticator = 0x00000000000000000000000000000000 Waking up in 3.8 seconds. Cleaning up request 0 ID 207 with timestamp +23 Cleaning up request 1 ID 208 with timestamp +23 Cleaning up request 2 ID 209 with timestamp +23 Cleaning up request 3 ID 210 with timestamp +23 Cleaning up request 4 ID 211 with timestamp +23 Waking up in 1.0 seconds. Cleaning up request 5 ID 212 with timestamp +23 Ready to process requests. # local test using: radtest testuser Secret149 localhost 0 testing123 rad_recv: Access-Request packet from host 127.0.0.1 port 45617, id=61, length=60 User-Name = "testuser" User-Password = "Secret149" NAS-IP-Address = 192.168.101.122 NAS-Port = 0 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns updated ++[files] returns noop [ldap] performing user authorization for testuser [ldap] expand: %{Stripped-User-Name} -> [ldap] expand: %{User-Name} -> testuser [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=testuser) [ldap] expand: dc=blackbox,dc=com -> dc=blackbox,dc=com rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in dc=blackbox,dc=com, with filter (uid=testuser) [ldap] checking if remote access for testuser is allowed by radiusFilterId [ldap] looking for check items in directory... [ldap] looking for reply items in directory... rlm_ldap: radiusFilterId -> Filter-Id = "TunnelMgtGroup" WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ldap] Setting Auth-Type = LDAP [ldap] user testuser authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = LDAP +- entering group LDAP {...} [ldap] login attempt by "testuser" with password "Secret149" [ldap] user DN: uid=testuser,ou=People,dc=blackbox,dc=com rlm_ldap: (re)connect to host20:389, authentication 1 rlm_ldap: bind as uid=testuser,ou=People,dc=blackbox,dc=com/Secret149 to host20:389 rlm_ldap: waiting for bind result ... rlm_ldap: Bind was successful [ldap] user testuser authenticated succesfully ++[ldap] returns ok +- entering group post-auth {...} ++[exec] returns noop Sending Access-Accept of id 61 to 127.0.0.1 port 45617 Filter-Id = "TunnelMgtGroup" Finished request 6. Going to the next request Waking up in 4.9 seconds. Cleaning up request 6 ID 61 with timestamp +218 Ready to process requests. thanks and best regards, Caius Pargar
hi, from your log... No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel [ttls] Got tunneled reply code 3 [ttls] Got tunneled Access-Reject [eap] Handler failed in EAP/ttls [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. when the EAP stuff kicks in, all the stuff is then sent to the inner-tunnel virtual server.....which needs to know what to do with the user... have you got your LDAP stuff in there? alan
Hi Alan, i checked my sites-available/inner-tunnel file: in authorize section everything is commented, except: eap and pap (ldap is commented). in authneticate section i have Auth-Type PAP { pap } Auth-Type LDAP { ldap } the rest is commented thanks and best regards, Caius Porgar --- On Mon, 11/16/09, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
From: Alan Buxey <A.L.M.Buxey@lboro.ac.uk> Subject: Re: FR2.1.7 with EAP-TTLS/PAP and LDAP To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Date: Monday, November 16, 2009, 12:00 PM hi,
from your log...
No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel [ttls] Got tunneled reply code 3 [ttls] Got tunneled Access-Reject [eap] Handler failed in EAP/ttls [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user.
when the EAP stuff kicks in, all the stuff is then sent to the inner-tunnel virtual server.....which needs to know what to do with the user... have you got your LDAP stuff in there?
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
Hi Alan,
i checked my sites-available/inner-tunnel file:
in authorize section everything is commented, except: eap and pap (ldap is commented).
in authneticate section i have Auth-Type PAP { pap }
Auth-Type LDAP { ldap }
the rest is commented
IIRC this is one of those wierd times when you need to have a DEFAULT Auth-Type := LDAP att he bottom of your users file. I may be wrong...but i think EAP+LDAP is a funny beast alan
Hi Alan, i told myself that i should try and enable the ldap module in the authorize section, nothing wrong in that ;) and now it works... so now in my inner-tunnel file i got: server inner-tunnel { authorize { suffix update control { Proxy-To-Realm := LOCAL } eap { ok = return } ldap expiration logintime pap } authenticate { Auth-Type PAP { pap } Auth-Type LDAP { ldap } } .... } it works like this, but im still not sure if this is the recommended way :D thanks and best regards Caius Pargar --- On Mon, 11/16/09, Alan Buxey <A.L.M.Buxey@lboro.ac.uk> wrote:
From: Alan Buxey <A.L.M.Buxey@lboro.ac.uk> Subject: Re: FR2.1.7 with EAP-TTLS/PAP and LDAP To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Date: Monday, November 16, 2009, 2:44 PM Hi,
Hi Alan,
i checked my sites-available/inner-tunnel file:
in authorize section everything is commented, except: eap and pap (ldap is commented).
in authneticate section i have Auth-Type PAP { pap }
Auth-Type LDAP { ldap }
the rest is commented
IIRC this is one of those wierd times when you need to have a
DEFAULT Auth-Type := LDAP
att he bottom of your users file. I may be wrong...but i think EAP+LDAP is a funny beast
alan
Caius wrote:
regarding your tips: a) i dont wanna do, maybe if i have no other choice, ill have 2 password attributes SSHA+NTLM, but its a clear no to clear-text, and a maybe to NT hash
NTLM is largely a version of MSCHAP for Active Directory. If you want to do PEAP authentication, you need clear-text passwords, or NT hashes.
b) need it, so not gonna happen
so, as i need to proceed further with my investigation, what are my options really? :D
i was thinking at the following: to do the normal user authentication in LDAP, based on the provided realm, and if no realm present authenticate the users in users file. Users which use 802.1x will be saved in clear-text in users file and users used for authentication for other stuff, will be checked in LDAP (@mydomain.com)
or can i switch this around? a user: myuser@dot1x.com will be based on the real authenticated in users file for 802.1x and a user with no realm will be authenticated in LDAP?
I would suggest using email addresses for 802.1X authentication. Inventing fake realms is a bad idea. Alan DeKok.
participants (4)
-
Alan Buxey -
Alan DeKok -
Caius -
tnt＠kalik.net