@lists.freeradius.org
Sent: Tuesday, September 6, 2011 1:28 PM
Subject: Re: Expiration Module Not Returning the Error Message
On Tue, Sep 6, 2011 at 11:41 AM, Det Det det.explo...@yahoo.com wrote:
Hi,
The expiration module works but it is not returning the error message.
Everytime I include the Expiration attribute
Hi,
The expiration module works but it is not returning the error message.
Everytime I include the Expiration attribute and set date accordingly. The user
is denied login. The reason is because the account expired and NOT because
there is no known good password found as shown below. How
On Tue, Sep 6, 2011 at 11:41 AM, Det Det det.explo...@yahoo.com wrote:
Hi,
The expiration module works but it is not returning the error message.
Everytime I include the Expiration attribute and set date accordingly. The
user is denied login. The reason is because the account expired
Ana Gallardo wrote:
I'm working with freeradius 2.1.8 and I want to return an attribute when
eexpiration module return 'userlock'.
I try to add the item in expiration module:
expiration {
Reply-Message = LA CUENTA HA EXPIRADO PARA
%{%{Stripped-User-Name}:-%{User-Name}}
Codigo
Hello,
I'm working with freeradius 2.1.8 and I want to return an attribute when
eexpiration module return 'userlock'.
I try to add the item in expiration module:
/etc/freeradius# cat modules-enabled/expiration
# -*- text -*-
#
# $Id$
expiration {
Reply-Message = LA CUENTA HA EXPIRADO PARA
Thanks a lot.
Reply-Message = LA CUENTA HA EXPIRADO PARA
%{%{Stripped-User-Name}:-%{User-Name}}
Codigo-Reject := Cuenta-Expirada
}
But it doesn't work.
Nothing in the documentation suggests that will work.
Sometimes I don't know where can I found what I'm looking for, so
[EMAIL PROTECTED] wrote:
Expiration is included in the server core, default configuration and
enabled by default. There is nothing you need to do in order to
implement it.
Is the wiki outdated on this point?
Point being?
If it is, perhaps it should/could be updated?
Regards,
How? By instructing you that you should actually read the existing
entries in the configuration - perhaps what you want is already there?
There are plenty of features that have been configured or disabled
(commented out) by default. You just have to read through the
configuration in order to find
Hi all!
I'm trying to implement expiration, as mentioned in the wiki at
http://wiki.freeradius.org/Radiusd.conf
But all this gives me is: Failed to link to module 'rlm_expiration':
rlm_expiration.so:
cannot open shared object file: No such file or directory
Is the wiki outdated on this point?
To: FreeRadius users mailing list
Subject: Re: Expiration Module
Jaco van Tonder [EMAIL PROTECTED] wrote:
It is never sent. I use radtest and get no replyradtest simply sends
the
request again and again...
OK. It works for me with the default reject_delay = 5. You've
set it to 1, which is something
Jaco van Tonder [EMAIL PROTECTED] wrote:
Thanks for the info. Setting it back to 5 did not help. But when I set it to
0 the reject is sent. Thus any value above 0 does not work.
Ok. I've fixed it.
Alan DekOk.
-
List info/subscribe/unsubscribe? See
Jaco van Tonder [EMAIL PROTECTED] wrote:
It is never sent. I use radtest and get no replyradtest simply sends the
request again and again...
OK. It works for me with the default reject_delay = 5. You've
set it to 1, which is something I haven't tested. Try setting it
BACK to the
I have downloaded the latest CVS snapshot (the 12th of June) and am running
it on Redhat 9 with Postgresql.
I have configured the expiration module and added an entry in the
radgroupcheck table. If I send a radius request to my server for a valid
user and the expiration date is set to later than
Jaco van Tonder [EMAIL PROTECTED] wrote:
if the expiration date/time has been reached - the
server traps this - but NO reply message is sent.
...
Delaying request 1 for 1 seconds
So... is it delayed for 1 second, or is it *never* sent?
My tests show it's only delayed for reject_delay
Subject: Re: Expiration Module
Jaco van Tonder [EMAIL PROTECTED] wrote:
if the expiration date/time has been reached - the
server traps this - but NO reply message is sent.
...
Delaying request 1 for 1 seconds
So... is it delayed for 1 second, or is it *never* sent?
My tests show it's only
Title: Expiration module
Hi,
Who can tell me in a few lines what the function of the expiration module is?
How does it work?
Thanks
Joris
Van Deuren Joris escreveu:
Hi,
Who can tell me in a few lines what the function of the expiration
module is?
How does it work?
I'm not sure if there is a module or not but I use the Expiration
attribute to automatically expire logins at a certain time (or date).
For example, you can use
Title: Expiration module
Hi,
I would like to do the following:
Using the unix shadow file for authentication.
If a user password will expire send a message to the console telling him that he must change his password.
If the user password has expired send a message to the console that his
to the console that his
password has expired.
Is this possible using the expiration module that is included in
freeradius?
The expiration module is not used for that.
Are there other ways to accomplish this behavior?
From a quick look at the code the unix module does not do that. It's a few
19 matches
Mail list logo