Re: Re: Re: SQL Authorization / Authentication

[Shannon Johnson]

Alan,   My users file isn’t very large. I’m not going to pretend to know what most of this means, but suffice it to say that I don’t have any dial-in users, so I’m not sure that the PPP, CSLIP, or SLIP parts apply. If they don’t, should I comment them out? Also, I don’t think the Default Auth-type should be System, but I didn’t see any other option, besides Reject. Is there an SQL option? The contents of my /etc/raddb/users file are as follows:     DEFAULT Auth-Type := System         Fall-Through = Yes   DEFAULT Service-Type == Framed-User         Framed-IP-Address = 255.255.255.254,         Framed-MTU = 576,         Service-Type = Framed-User,         Fall-Through = Yes   DEFAULT Framed-Protocol == PPP         Framed-Protocol = PPP,         Framed-Compression = Van-Jacobson-TCP-IP   DEFAULT Hint == "CSLIP"         Framed-Protocol = SLIP,         Framed-Compression = Van-Jacobson-TCP-IP   DEFAULT Hint == "SLIP"         Framed-Protocol = SLIP     Shannon     "Shannon Johnson" <[EMAIL PROTECTED]> wrote: > That's what I thought, but the definition of Authorization and > Authentication got me a little confused. New question now... ... > rlm_sql (sql): User  not found in radgroupcheck > rlm_sql (sql): User not found > rlm_sql (sql): Released sql socket id: 2 >   modcall[authorize]: module "sql" returns notfound ... > From what I can tell, it's not passing the username (or password, for > that matter) to the SQL database. Would that be a correct assumption? If > so, do you have any suggestions on what to do to fix?     Look through the SQL configuration, seeing why the user doesn't match.     I'd suggest debugging it with the 'users' file first, though.  Get the config working for the user, and then move it over to SQL.  That way you're tracking down one problem at a time.     Alan DeKok.