Learn more about these different git repos.
Other Git URLs
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.
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.
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.
Filed https://bugs.kde.org/show_bug.cgi?id=248304
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'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.
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
Fields changed
priority: minor => major
owner: somebody => sbose
fixed in 9468a58
resolution: => fixed status: new => closed
rhbz: => 0
Metadata Update from @orion: - Issue assigned to sbose - Issue set to the milestone: SSSD 1.5.0
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/1646
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.