Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues authenticating after resuming from suspend while on wireless #2144

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1102


https://bugzilla.redhat.com/show_bug.cgi?id=754511

Description of problem:
This issue presents itself by preventing you from unlocking the screen after
resuming from suspend.  This scenario only occurs when you were connected to a
wireless network when the laptop entered suspend mode.  When resuming, all
password attempts fail until you either restart SSSD or connect to an ethernet
connection.

Version-Release number of selected component (if applicable):
sssd-1.5.1-66.el6.x86_64
openldap-clients-2.4.23-15.el6_1.3.x86_64
openldap-2.4.23-15.el6_1.3.x86_64

How reproducible:
roughly 90% of the time

Steps to Reproduce:
1. Connect to Red Hat secure wireless network
2. Suspend your laptop
3. Leave the system suspended for at least 1 minute
4. Resume the system from suspend
5. Attempt to unlock screen

Actual results:
Failed login attempts

Expected results:
The login should revert to cached local SSSD information


Additional info:
This only seems to manifest itself right now when connecting to secure Red Hat
wireless network (with RSA token)

Comments


Comment from mattymo at 2011-12-01 14:57:52

Fields changed

cc: => mmosesoh@redhat.com
coverity: =>
patch: => 0
rhbz: =>
tests: => 0
testsupdated: => 0
upgrade: => 0


Comment from dpal at 2011-12-01 15:52:07

Fields changed

description: https://bugzilla.redhat.com/show_bug.cgi?id=754511

{{{
Description of problem:
This issue presents itself by preventing you from unlocking the screen after
resuming from suspend. This scenario only occurs when you were connected to a
wireless network when the laptop entered suspend mode. When resuming, all
password attempts fail until you either restart SSSD or connect to an ethernet
connection.

Version-Release number of selected component (if applicable):
sssd-1.5.1-66.el6.x86_64
openldap-clients-2.4.23-15.el6_1.3.x86_64
openldap-2.4.23-15.el6_1.3.x86_64

How reproducible:
roughly 90% of the time

Steps to Reproduce:

  1. Connect to Red Hat secure wireless network
  2. Suspend your laptop
  3. Leave the system suspended for at least 1 minute
  4. Resume the system from suspend
  5. Attempt to unlock screen

Actual results:
Failed login attempts

Expected results:
The login should revert to cached local SSSD information

Additional info:
This only seems to manifest itself right now when connecting to secure Red Hat
wireless network (with RSA token)
}}}
=> https://bugzilla.redhat.com/show_bug.cgi?id=754511

{{{
Description of problem:
This issue presents itself by preventing you from unlocking the screen after
resuming from suspend. This scenario only occurs when you were connected to a
wireless network when the laptop entered suspend mode. When resuming, all
password attempts fail until you either restart SSSD or connect to an ethernet
connection.

Version-Release number of selected component (if applicable):
sssd-1.5.1-66.el6.x86_64
openldap-clients-2.4.23-15.el6_1.3.x86_64
openldap-2.4.23-15.el6_1.3.x86_64

How reproducible:
roughly 90% of the time

Steps to Reproduce:

  1. Connect to Red Hat secure wireless network
  2. Suspend your laptop
  3. Leave the system suspended for at least 1 minute
  4. Resume the system from suspend
  5. Attempt to unlock screen

Actual results:
Failed login attempts

Expected results:
The login should revert to cached local SSSD information

Additional info:
This only seems to manifest itself right now when connecting to secure Red Hat
wireless network (with RSA token)
}}}

milestone: NEEDS_TRIAGE => SSSD 1.8.0
owner: somebody => jhrozek


Comment from mkosek at 2011-12-16 16:04:35

Fields changed

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=754511 754511]


Comment from sgallagh at 2012-02-27 19:52:26

We have been able to reproduce this. We'll continue trying to reproduce it, but we're not going to hold up 1.8.0 for it.

blockedby: =>
blocking: =>
feature_milestone: =>
milestone: SSSD 1.8.0 (LTM) => SSSD 1.8.1 (LTM)


Comment from mattymo at 2012-02-27 20:00:54

Steve,

I haven't been able to reproduce this since November. You should just close this out.


Comment from sgallagh at 2012-02-27 20:06:51

Ok, thanks. My original suspicion was that this might actually have been an openldap bug, not an SSSD issue. As an openldap update occurred in September, I'm inclined to believe I was correct.

Thanks!

resolution: => worksforme
status: new => closed


Comment from jhrozek at 2012-02-27 22:35:00

Replying to [comment:5 mattymo]:

Steve,

I haven't been able to reproduce this since November. You should just close this out.

One more note -- when I was trying to reproduce the bug, I ran into an SELinux issue with the exact versions of SSSD and openldap packages you described in the bugzilla. I haven't checked if the issue is still present with the latest 6.3 candidate packages, but it you changed the SELinux status from Enforcing to Permissive, that might be the reason that "fixed" the bug for you.

I'll retest and reopen the bug if I can still reproduce the SELinux denial with 6.3 packages tomorrow.


Comment from jhrozek at 2012-03-02 14:48:41

Replying to [comment:7 jhrozek]:

Replying to [comment:5 mattymo]:

Steve,

I haven't been able to reproduce this since November. You should just close this out.

One more note -- when I was trying to reproduce the bug, I ran into an SELinux issue with the exact versions of SSSD and openldap packages you described in the bugzilla. I haven't checked if the issue is still present with the latest 6.3 candidate packages, but it you changed the SELinux status from Enforcing to Permissive, that might be the reason that "fixed" the bug for you.

I'll retest and reopen the bug if I can still reproduce the SELinux denial with 6.3 packages tomorrow.

Just to put a closure here - the SELinux denial I was seeing is now being tracked by https://bugzilla.redhat.com/show_bug.cgi?id=799322


Comment from sgallagh at 2017-02-24 14:56:04

Metadata Update from @sgallagh:

  • Issue assigned to jhrozek
  • Issue set to the milestone: SSSD 1.8.1 (LTM)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants