You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to turn off the "Authenticated with cached credentials" message. With kdm login it pops up a dialog box that must be responded to before login continues. Annoying and I don't care if I was authenticated with cached credentials or not.
This is something we CAN do, but I question whether it doesn't make more sense to have KDM fix their message reporting. For example, in GDM, this message flashes on the screen for about one second (just long enough to read it) then it disappears.
There are certain to be other PAM modules that produce output, and it would be a better solution for KDM to handle them gracefully.
Another point to note: this behavior is desired if {{{offline_credentials_expiration}}} is specified in sssd.conf, as it lets the user know how long they have until they need to perform an online login or be locked out.
Well, upstream closed as wontfix. Not sure you want to weigh in there or not. Is there a different category of PAM_TEXT_* messages that would indicate more importance and the need for confirmation (expiration for e.g.)?
I propose the following behavior:
Add a new option: {{{pam_verbosity}}} which will default to zero (which means only important messages, like the offline expiration warnings)
We will have the "Authenticated with cached credentials message" (without expiration warning) appear at a higher verbosity.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/604
I would like to be able to turn off the "Authenticated with cached credentials" message. With kdm login it pops up a dialog box that must be responded to before login continues. Annoying and I don't care if I was authenticated with cached credentials or not.
Comments
Comment from sgallagh at 2010-08-18 21:09:46
This is something we CAN do, but I question whether it doesn't make more sense to have KDM fix their message reporting. For example, in GDM, this message flashes on the screen for about one second (just long enough to read it) then it disappears.
There are certain to be other PAM modules that produce output, and it would be a better solution for KDM to handle them gracefully.
Comment from orion at 2010-08-18 21:12:49
Ah, didn't know about the GDM behavior. Must be how they handle PAM_TEXT_INFO messages? I'll poke around in kdm some more.
Comment from sgallagh at 2010-08-18 21:15:39
Yes, it's a PAM_TEXT_INFO reply.
Another point to note: this behavior is desired if {{{offline_credentials_expiration}}} is specified in sssd.conf, as it lets the user know how long they have until they need to perform an online login or be locked out.
Comment from orion at 2010-08-18 23:26:48
Filed https://bugs.kde.org/show_bug.cgi?id=248304
Comment from orion at 2010-08-19 16:48:31
Well, upstream closed as wontfix. Not sure you want to weigh in there or not. Is there a different category of PAM_TEXT_* messages that would indicate more importance and the need for confirmation (expiration for e.g.)?
Comment from sgallagh at 2010-08-19 16:53:39
I'm not opposed to making this message optional.
I propose the following behavior:
Add a new option: {{{pam_verbosity}}} which will default to zero (which means only important messages, like the offline expiration warnings)
We will have the "Authenticated with cached credentials message" (without expiration warning) appear at a higher verbosity.
Comment from sgallagh at 2010-08-24 14:57:25
Time is limited for 1.4.0. Targeting 1.5.0.
If time permits, we will pull it up to 1.4.0.
doc: 0 => 1
milestone: NEEDS_TRIAGE => SSSD 1.5.0
owner: sbose => somebody
tests: 0 => 1
Comment from dpal at 2010-10-19 15:55:39
Fields changed
priority: minor => major
Comment from sbose at 2010-10-20 14:11:47
Fields changed
owner: somebody => sbose
Comment from sbose at 2010-11-16 11:28:55
fixed in 9468a58
resolution: => fixed
status: new => closed
Comment from dpal at 2012-01-19 02:56:55
Fields changed
rhbz: => 0
Comment from orion at 2017-02-24 15:02:33
Metadata Update from @orion:
The text was updated successfully, but these errors were encountered: