2018-02-13 - Re: [GRASE-Hotspot] call broker while login process

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 48df9a4c6f9882d879050aa77d1bfac7a95b7468b4c297ce43b37ce9f7d122cc
Message ID: <CAESLx0JvQxjepZjOhkA+ASdYugQwZYSQfOLAAX1-BCH6my4SfA@mail.gmail.com>
Reply To: <314ba989-fa50-422c-89df-e3378290abaf@grasehotspot.org>
UTC Datetime: 2018-02-13 14:41:35 UTC
Raw Date: Wed, 14 Feb 2018 07:41:35 +1000

Raw message 

Ah. That makes more sense now. I had it backwards to what you were trying to do.

I would start by seeing if your existing system can provide RADIUS
based authentication. If it can, you don't need the Grase Hotspot
backend at all, and can instead connect Coova Chilli (the captive
portal part) directly to your main system. The login process is a
RADIUS login, so you can't really hook into it, you need to replace
the backend that it's talking to.

Regards

Tim

On 14 February 2018 at 06:56, 'Stephan Stein' via Grase Hotspot
<gr***t@grasehotspot.org> wrote:
> Hi Tim
>
> Sure, but on which http/php page I could hook into the login process?
>
> --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gr***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at https://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/314ba989-fa50-422c-89df-e3378290abaf%40grasehotspot.org.

Thread