Automating Authentication Profiles for Splash Page
-
Hi all,
New to Netgate and seeking some advice on how to best automate, or otherwise find the most efficient way to create guest profiles for authentication, using guests' last name for example.
The aim is to easily create login details for guests staying in a small hotel, valid for the duration of their stay.
Guest details can be stored in a spreadsheet for example, along with the duration of their stay.
Is there any way to somehow automate this? Any advice would be appreciated. Even a link to some documentation or tutorial would be great.
Thanks in advance.
-
Hi,
@Bashlory said in Automating Authentication Profiles for Splash Page:
The aim is to easily create login details for guests staying in a small hotel, valid for the duration of their stay.
Yeah. And while you're at it, use the hotel's PMS so that during check-in the accounts gets created and activated, and during check-out the account is destroyed.
I managed to implement such a thing with pfSense, it worked well.
And true, the receptionist doesn't need to have access to pfSense or anything.pfSense and the captive portal have several option to identify the visitors : user/password or vouchers, you can also use the package FreeRaduis to do basically the same thing, with much more control over how long, how much etc. Even OTP is possible.
Btw : I had to edited the way how FreeRadius config files were created, so it uses the SQL database in stead a flat text file for user identification. Now I could "inject" new users, password and other details into the SQL database from other sources in the network, like the PMS adding and deleting users without having to change FreeRadius settings in pfSense.
The down side was : I had to manually edit the package source files, and create the facility for the PMS to drop user info into the database, something that has to be taken care after every update on both sides. Not really a problem for me, as I can do it remotely. And most and for all : it 'my' pfSense, and it's 'my' hotel, I'm in control, and I need no one to take care of things when there are issues, I just need my hands and head.
And yes, some basic PHP (Python, shell script etc) is not an option here. Actually, you have to know how things really work before you start changing them.I finally choose to have logins user names like 101, 102 103 104 etc, our room numbers.
The small booklet in the room the "room directory", on the first page, right after the "Read me first" I mention a room unique password.
I never change these passwords. This works great for many years now. Actually, it's just perfect since pfSense was created (forked) , a decade ago.I advise you to go for the most important atomisation design rule : "Keep It Simple".
@Bashlory said in Automating Authentication Profiles for Splash Page:
valid for the duration of their stay.
Not really needed, because, when a clients leaves, they won't be able connect any more ;)
