Did you set the reply message in radiusd.conf?

#
        # The expiration module. This handles the Expiration attribute
        # It should be included in the *end* of the authorize section
        # in order to handle user Expiration. It should also be included
        # in the instantiate section in order to register the Expiration
        # compare function
        #
        expiration {
                #
                # The Reply-Message which will be sent back in case the
                # account has expired. Dynamic substitution is supported
                #
                reply-message = "Password Has Expired\r\n"
#               reply-message = "Your account has expired, %{User-Name}\r\n"
        }

Ivan Kalik
Kalik Informatika ISP


Dana 14/3/2007, "PD" <[EMAIL PROTECTED]> piše:

>I think the same too... cause expiration is not the new attribute.
>
>The expiration attribute itself working fine, the only problem is no
>explanation to user when the system reject him/her.
>
>CMIIW
>
>PD
>On 3/14/2007, "Alan DeKok" <[EMAIL PROTECTED]> wrote:
>
>>PD wrote:
>>> I am using FR 1.1.4 build from FBSD port
>>> do I need to load the module ?
>>
>>  No.  If it's not in 1.1.5, it's not in any prior version, either.
>>
>>  Alan DeKok.
>>--
>>  http://deployingradius.com       - The web site of the book
>>  http://deployingradius.com/blog/ - The blog
>>-
>>List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>>
>>
>
>-
>List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
>

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to