#2335 Investigate using the krb5 responder for driving the PAM conversation with OTPs
Closed: Fixed None Opened 6 years ago by jhrozek.

We need logic in SSSD that would allow the GDM prompter to prompt the user for long-term password and the OTP in different prompts.

Nathaniel suggested to use the krb5 responder callback. Citing from his proposal:

That is, the user name is selected in GDM and SSSD begins the krb5 connection. The responder callback is called. Within this callback, SSSD can see exactly what mechanisms can be used to authenticate the user. No connection to LDAP is needed. This should drive the responses (all within the callback). There is no guarantee that SSSD’s analysis of LDAP will drive the choices actually available in the responder callback.

However, I don’t know how this could be done while preserving the communication protocol between the parent and child processes.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.1
priority: major => blocker

Fields changed

cc: => nalin

Defer cloning, may be linked with an OTP tracker later.

rhbz: => todo

Fields changed

blockedby: => 2404

as discussed on a meeting this week, we are not going to implement the changes in 1.12, but rather in 1.13 together with smart card work.

milestone: SSSD 1.12.1 => SSSD 1.13 beta

Fields changed

mark: => 1

Fields changed

owner: somebody => sbose
status: new => assigned

Fields changed

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to sbose
- Issue marked as depending on: #2404
- Issue set to the milestone: SSSD 1.13.1

3 years ago

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/3377

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata