#2752 Detect captive portals and make sure SSSD treats networks with them as offline
Opened 3 years ago by abbra. Modified 2 years ago

When demonstrating KDC proxy functionality at GUADEC I've found out that SSSD is not being able to treat captive portals as offline environment.

In case of captive portal, a network is available but you cannot get beyond DNS and captive portal website until you enter a password or a code in browser. Thus, SSSD fails to authenticate with KDC proxy but has not properly pushing itself into offline state so that only first factor might be used for offline authentication.

At some point SSSD puts itself in a such state that no password is accepted and you have to have a local account to actually pass through the captive portal.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 beta

Fields changed

rhbz: => todo

Note: NetworkManager has centralized system-wide captive portal detection & handling. I guess that SSSD should somehow hook on NM interface (when available) and do not re-invent the wheel.

cc: => pspacek

I agree, there was a blog post about this topic on Planet Fedora recently which made me think the same.

We might want to hook into the NM interface either way since many setups only configure a local resolver, but the 1.14 buckets are already quite large, so this is a nice-to-have for 1.14.

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Metadata Update from @abbra:
- Issue set to the milestone: SSSD Future releases (no date set yet)

2 years ago

Login to comment on this ticket.

Metadata