#3883 A proper message asking to insert smartcard when with-smartcard-required is enabled on authselect and trying to login without smartcard
Closed: cloned-to-github 2 years ago by pbrezina. Opened 3 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla: Bug 1645249

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
A proper message asking to insert smartcard when with-smartcard-required is
enabled on authselect and trying to login without smartcard

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. authselect select sssd with-smartcard with-mkhomedir with-smartcard-required
with-smartcard-lock-on-removal
2. Configure sssd.conf as follows:
[root@dhcp129-152 ~]# cat /etc/sssd/sssd.conf
[sssd]
services = nss, pam
domains = shadowutils

[nss]

[pam]
pam_cert_auth = True
debug_level = 9

[domain/shadowutils]
id_provider = files
debug_level = 9

[certmap/shadowutils/testcardholder]
matchrule = <SUBJECT>.*CN=Test Cardholder.*


3. Do not insert any smartcard and go to gdm login screen

Actual results:
Password prompt

Expected results:
A message to insert a smartcard

Additional info:
Seeing the same issue after a screen lock on smartcard removal and smartcard no
inserted back when trying to unlock.

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1645249

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1

3 years ago

There is an authselect bug: https://bugzilla.redhat.com/show_bug.cgi?id=1674397 I'm not sure yet which component is the problematic one.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

2 years ago

Metadata Update from @pbrezina:
- Issue tagged with: bugzilla

2 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/4870

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.

Metadata Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata