Changed Captive Portal / best practise to maintain private/individual changes



  • Hi all,

    I have changed the captive portal login.php in order to allow my users to authenticate against a REST Service we are using in out network (please no flames about this - it is what it is). Is there a best practise to maintain such change in order to be able to reapply it once pfsense updates change login.php in the future? At the moment I am keeping it in a diff file to be used by patch…

    thanks for any pointers

    cheers
    Torsten



  • System Patches package lets you record patches, apply them, and (at least attempt to) reapply them after an upgrade.

    If the service you are authenticating against is not a completely one-off in-house thing, then you could submit the changes on GitHub as an extra feature.



  • Thanks for that pointer, I will check this package out.

    I suppose the system I authenticate against is kinda arcane. I run pfsense to manage the network on a leisure flying airport. Our club uses a cloud based system to manage reservations, flights, licenses etc - the whole 9 yards. This system has a REST interface against which I authenticate pilots wanting to access our network. This system is in use roughly by about 250 clubs in Germany. So, it is not completely arcane - but on a global scale it's probably completely irrelevant :-)

    cheers
    Torsten