Re: [Captive-portals] client identifying info between API and enforcement

Erik Kline wrote: > I was expecting this is what might be required, given the > architectures that are currently in use: I think that I got you, but I need a picture. > [3] login service updates enforcement point about token_1's state > (assuming login success)

Re: [Captive-portals] client identifying info between API and enforcement

On 28 October 2017 at 21:41, Kyle Larose wrote: >> It strikes me that we should hear again about the extra information >> in >> the proposed ICMP option. I'm wondering if it could be made more >> opaque to the client, maybe boil it down to just the SESSION_ID > > I've also