PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001460 | PacketFence | configuration | public | 2012-06-04 12:57 | 2015-02-13 15:42 |
| Reporter | obilodeau | ||||
| Assigned To | |||||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0001460: activation_domain should be configurable | ||||
| Description | The guest email activation allows for an activation_domain to override the normal hostname.domainname value provided in pf.conf. This is generally useful to expose the PacketFence guest activation to the broader Internet through an Internet visible domainname. Currently the parameter is overridable in pf::web::custom but it should be feasible to do so in configuration files. The reason why I haven't implemented it right away is that it's default value will be emtpy ('') and this should fallback to the hostname.domainname default. However our admin system currently doesn't support very well empty pf.conf values or empty defaults (to be confirmed). | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2012-06-04 12:57 | obilodeau | New Issue | |||
| 2015-02-13 15:42 | lmunro | Note Added: 0003803 | |||
| 2015-02-13 15:42 | lmunro | Status | new => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||