Hi, > I've seen the discussion about this and I'd like to see if we can help > moving the issues related to this topic. Our deployment plan requires > the integration of the registration / captive portal in the intranet > site to have a single access point (login place). It seems that captive > portal and administration interface are mostly decoupled, though there > is not so much documentation on the captive portal callbacks or required > urls and its arguments/usages. > > Do you think it could be usefull to document this information? or should > we do this integration in a more 'local/internal' branch? I am not sure we want to go over kind of SSO for now, so you should probably (to my perspective) do the changes in a local branch.
For the interactions, if you know perl a little, just have a look into the register.cgi file. Main calls are in lib/pf/web.pm. Thanks! -- Francois Gaudreault, ing. jr fgaudrea...@inverse.ca :: +1.514.447.4918 (x130) :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ PacketFence-devel mailing list PacketFence-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-devel
