| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001411 | PacketFence | guests | public | 2012-03-29 14:35 | 2015-02-13 15:42 |
|
| Reporter | obilodeau | |
| Assigned To | | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001411: fix bad categorization of pre-registered guests |
| Description | Right now, a self-registered guest who registers in advance (remotely) gets an entry created in temporary_password and is authenticated in the system through authentication::preregistered_guests.
Problem with that is that the category applied to such a guest is the one configured by: [guests_admin_registration].category. Which should be the category for administrators-created guest accounts.
To fix: target category should be in temporary_password table to support preregistration properly. preregistered_guests then just feeds the category from the table to the user who authenticated.
Workarounds can be performed by users by modifying their conf/authentication/preregistered_guests.pm... module logic.
Bump if you feel this is important. |
| Tags | No tags attached. |
|
| fixed in git revision | |
| fixed in mtn revision | |
|
| Attached Files | |
|
Relationships 
Relationships 