--On Tuesday, November 10, 2009 17:14:32 +0000 Jeremy Skelton
<[email protected]> wrote:
Has anyone got a working example custom webauth login page they would be
willing to share. I've got one mostly working which I based on the
default page with major formatting changes - but it is failing at the
last hurdle - the login part works, as do the commercial certificates
which I have uploaded to encrypt the loging details, but it won't
re-direct to the originally requested web page.
Interestingly, the default page shows the same problem if I upload it as
a custom page (along with the loginscript.js file that it calls), so I
think the problem may be either the location, or that it is called
differently, or maybe I need some other file that is present at the
default location and I haven't copied.
The default page is called with URL such as
https://webauth.wism.lse.ac.uk/login.html?redirect=www.cisco.com/, and
the custom page with
https://webauth.wism.lse.ac.uk/fs/customwebauth/login.html?switch_url=ht
tps://webauth.wism.lse.ac.uk/login.html&ap_mac=00:19:07:8e:f9:30&wlan=tw
a&redirect=www.cisco.com
As a bit of background, we currently have two WiSMs (one each in two of
our four 6509s, which will become six before long) and around 270 APs.
We will get a third WiSM for when we break the 300 AP barrier. The WiSMs
are running version 6.0.182.0. We have 802.1x working OK but not widely
deployed for other reasons, and also unauthenticated pass-through to our
Bluesocket gateways which are currently under pressure, which is why we
are pursuing the WiSM web authentication route as a half-way house
towards 802.1x everywhere. We have purchased and uploaded commercial
certificates for the
I've got a support call open with our supplier, but I don't think this
is a widely used feature so there isn't a lot of experience around and
they haven't provided an answer. Any assistance will be gratefully
received.
Jeremy Skelton, London School of Economics IT Service
Hi Jeremy,
We specifically redirect to our homepage, so our config probably wouldn't
help you. However I notice that the bit I commented out in loginscript.js
has this:
var searchString = "?redirect=";
at least with our WiSMs the redirect is added as the last URL argument i.e.
?blah=a&foo=bar&redirect=URL
so in order to catch the URL you would need to change the JS to something
like:
var searchString = '&redirect=';
does that correlate with your situation ?
-James
--
James J J Hooper
Network Specialist
Information Services
University of Bristol
http://www.wireless.bristol.ac.uk http://www.jamesjj.net
--
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
