Tech Forum

I've got set up in our stake a web based authentication method.

The stake maintains a list of user names that are allowed. It is tied into LDS Account to check passwords.

It works great! I'm wondering if it is possible to add this type of idea to the project to provide internet access to members to fulfill there callings. You can grant access and revoke access as needed without needing to change the WEP key.

This sounds great. Can you provide information on how that was accomplished for others to do the same?

The setup is complicated, but I want to work with the network department at church headquarters to make it available to any who desire.

It requires having a radius server, a https server, reflashing a router with OpenWRT and installing ChilliSpot.

If the church is involved then we can use a single radius and https (which the church already has) and I'd be willing to set up the router and then the local people would only have to plug in wires and learn how to add and remove access through the https server.

davereb wrote:I've got set up in our stake a web based authentication method.

The stake maintains a list of user names that are allowed. It is tied into LDS Account to check passwords.

It works great! I'm wondering if it is possible to add this type of idea to the project to provide internet access to members to fulfill there callings. You can grant access and revoke access as needed without needing to change the WEP key.

Please contact me by private message to discuss this.

This probably goes without saying but I thought that I would remind everone that we should never cache LDSAccount credentials on any non-official computer or server.

Tom

tomw wrote:This probably goes without saying but I thought that I would remind everone that we should never cache LDSAccount credentials on any non-official computer or server.

Tom

I agree, and just for the record, I test the passwords at each request and do not store them on my server.

Personally, I'd never give my LDS Account information to any non-Church server. I didn't say anything in this situation since it was for access to the Church WiFi.

It does sound like something I'd like the see the church setup to help us manage our AP access.

RussellHltn wrote:Personally, I'd never give my LDS Account information to any non-Church server. I didn't say anything in this situation since it was for access to the Church WiFi.

It does sound like something I'd like the see the church setup to help us manage our AP access.

I would love to see the church implement this as an official option to units that want it. I'd love to help with the implementation.

Our stake presidency has been looking for a solution like this also. I like the concept of the church hosting the server and giving controls at the local level (e.g. lock access during Sacrament meeting, time out connections after a certain time, logs of who is using the internet and what sites, easier access for members).

Currently the hardware that I am using is not big enough to track which sites are visited, but it does log the user, time, and data transferred.

With a more expensive router it should be able to handle logging non ssl sites. (possibly the ip of ssl sites) But, I've not tried this yet.