Learn more about these different git repos.
Other Git URLs
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
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)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3793
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.