Hi Tim, > If one configures the guest portal to allow for self-registration and > limits the access to something like 3 weeks before automatically > dropping the registration, is there a configuration that would allow for > blocking that device for a period of time whether indefinite or time > specified so that a guest can’t just keep automatically > self-registering? We do not have this feature in PacketFence right now BUT we can (I think) easily do it. Here is my idea : - Tweak the core to either NOT reset the regdate on a node deregister OR add a new field called "previous registration". - Add a check in the self-registration page to check if the regdate (or previous registration) field value is in a given interval (3 hours ago to NOW), if it's older than 3 hours, allow it again.
> We would prefer to have a policy of flexibility for > short term guests, but require a college network account for long term > guests. I am curious if this has that capability? I don't see issues with that. We can define different policies depending of the user type. Thanks! -- Francois Gaudreault, ing. jr [email protected] :: +1.514.447.4918 (x130) :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
