PacketFence - BTS - PacketFence
View Issue Details
0001704PacketFenceguestspublic2013-09-03 07:322015-02-18 11:27
0001704: Guest expiration is not set using the temporary_password method
The default 31D expatiation of the password is never set in 4.0.5 code. It defaults to 0000-00-00 00:00:00

This makes the guest authentication per email fail, since it requires the expatriation date.

commenting the function in at line 309
        'expiration',"0000-00-00 00:00:00"

in temporary fixxes this issue and sets the default of 31 days
No tags attached.
Issue History
2013-09-03 07:32maikelNew Issue
2013-09-04 15:06francisNote Added: 0003437
2013-09-05 11:33maikelNote Added: 0003438
2015-02-18 11:27lmunroAssigned To => jrouzier
2015-02-18 11:27lmunroStatusnew => assigned

2013-09-04 15:06   
How do you create your users?

When you use the Web admin interface, the hardcoded default expiration of 31 days will never be used simply because the expiration must be specified when submitting the form.

Notice that what is called the "expiration" is the end date of the registration window.
2013-09-05 11:33   
Users are created using the self registration method. Thats using a custom code block though to set the userid to the swich alias command.

So the user is actually succesfully added using the /activate/email cgi code

There indeed this is not set in the field thus not send. Noticed the only way to get the hardcoded 31D in there to remove the update_field_for_action code. Else the experation is not set