Re: (RADIATOR) Update LDAP dir from Radiator

1999-06-23 Thread Anonymous
> > I have been asked to implement Radiator on a site using an LDAP server as > a user database. They have some extra requirements: > 1 On succesful login the current time has to be put in an attribute in the > users entry > 2 While the user has an active session the ip address he was allocated

(RADIATOR) NoDefaultIfFound and Fall-Through

1999-06-23 Thread Anonymous
Hi All, Just wondering if it is possible to get NoDefaultIfFound and Fall-Through to work together. We have an AuthBy FILE file which has some users with passwords in the file, some with passwords in AuthBy SYSTEM. The default user has their password in AuthBy SYSTEM. Some users have pas

Re: (RADIATOR) Strange attributes from Xyplex

1999-06-23 Thread Anonymous
> Anyone seen this before? > > This is an accounting packet from a Xyplex NAS. Note the very unusual > Acct-Session-Id. Can anyone shed any light on why a Xyplex does this, and how > to stop it? If you issue a 'def server identification ', it will prepend the ": " to the Acct-Session-Id. I wo

Re: (RADIATOR) Update LDAP dir from Radiator

1999-06-23 Thread Anonymous
Hi Paul, I must agree with a previous poster on this topic: Putting that data into LDAP is not really what LDAP was designed for. If you really have to do it, you could do it by adding a PostAuthHook, and at least avoid having to change the distributed Radiator code. Hope that helps. Cheers.

(RADIATOR) db: do failed

1999-06-23 Thread Anonymous
Hi. Just installed the latest Radiator with all patches talking to an SQL database. However we have suddenly started seeing these messages: [root@ankh etc]# DB::Synapse::dB do failed: Server message number=233 severity=16 state=2 line=1 server=SOLOMON text=The column User Name in table Calls ma